00:04.39 |
brlcad |
ar cru .libs/libpng.a example.o ...
pngwtran.o pngwutil.o~ranlib .libs/libpng.a for example |
00:05.03 |
brlcad |
~ww |
00:05.07 |
ibot |
There is no such thing as the wrong window,
just wrong people |
00:30.49 |
jano |
ergh |
00:30.54 |
jano |
i want to go take more pictures. |
00:30.56 |
jano |
:D |
02:16.36 |
*** join/#brlcad EricWilhelm
(~ewilhelm@adsl-208-191-39-126.dsl.tpkaks.swbell.net) |
02:45.28 |
*** join/#brlcad tjyang
(~Administr@c-67-175-74-12.client.comcast.net) |
03:50.27 |
starseeker |
brlcad - did full build of current cvs - no
luck :-( |
03:51.40 |
starseeker |
talk about an annoying problem |
04:09.13 |
brlcad |
starseeker: looking at that now |
04:09.19 |
brlcad |
looks like a different issue that the
others |
05:52.07 |
CIA-6 |
BRL-CAD: 03brlcad * 10brlcad/acinclude.m4:
update libtool.m4 source to 1.5.10's. apply s/~$RANLIB/ ; $RANLIB/
fix so that libtool 1.5 on os x doesn't choke on the ~ |
07:20.52 |
CIA-6 |
BRL-CAD: 03brlcad * 10brlcad/autogen.sh: fix
encounters with version numbers that don't have a patch number
(e.g. libtool 1.5), also fix version checks to actually stop
checking minor/patch numbers if our major/minor are greater than
required. |
13:58.17 |
*** join/#brlcad kraig01
(~kraig@dsl-63-173-191-32.tcq.net) |
15:29.23 |
brlcad |
starseeker: made some changes that hopefully
fix the sandbox problem.. |
15:30.40 |
brlcad |
starseeker: a cvs status on configure.ac
should show 14.24 when you are up to date |
15:37.06 |
Nidhoggr |
I couldn't find my dev cd last night. you'd
think if you could download xcode online, you could download the
x11 sdk. |
15:45.19 |
brlcad |
oof |
15:45.29 |
brlcad |
Nidhoggr: looking now, i've got that disc
here |
15:45.37 |
Nidhoggr |
cool, thanks. |
15:49.50 |
Nidhoggr |
no wonder brlcad is so pokey. |
15:49.57 |
Nidhoggr |
he keeps getting poked. |
15:50.02 |
jano |
everyone poke! |
15:50.15 |
jano |
awee |
15:50.29 |
Nidhoggr |
eek! |
15:52.44 |
brlcad |
~poke jano |
15:52.46 |
ibot |
but then who will poke the pokers,
brlcad? |
15:54.35 |
jano |
that's right |
15:59.11 |
brlcad |
Nidhoggr: uploaded to secretplace in my home
as X11SDK.pkg.tar.gz |
15:59.43 |
Nidhoggr |
thank you very much, brlcad !!! |
16:01.33 |
brlcad |
heh, thank me when it compiles |
16:01.46 |
brlcad |
damn me before then |
16:01.54 |
Nidhoggr |
:) |
16:30.12 |
Nidhoggr |
brlcad: any estimate how long to compile on
1.3 ghz powerbook g4 with 1 gb ram? |
16:30.25 |
Nidhoggr |
it's doing pretty good so far. |
16:36.14 |
brlcad |
half hour or so would be my guess |
16:36.20 |
Nidhoggr |
cool |
16:41.42 |
Nidhoggr |
make completes, but make install errors.
:) |
16:41.53 |
brlcad |
ahh, yes.. cvs up ;) |
16:42.09 |
brlcad |
dang.. forgot to mention that..
*blush* |
16:42.09 |
Nidhoggr |
hrm. I'm using the tarball you sent. |
16:42.12 |
Nidhoggr |
hang on. |
16:42.31 |
brlcad |
ahh, yes .. same problem on the
tarball |
16:42.48 |
Nidhoggr |
can I just fix the ~ranlib thing? |
16:43.24 |
brlcad |
yes |
16:43.32 |
Nidhoggr |
it's doing ~ranlib instead of ;
ranlib |
16:43.57 |
brlcad |
replace all "~" in acinclude.m4 with " ;
" |
16:45.06 |
brlcad |
perl -pi -e "s/~/ ; /" acinclude.m4 |
16:46.01 |
brlcad |
er, oop s/~/ ; /g |
16:49.37 |
Nidhoggr |
do I need to do "make" again, etc? or will it
work with just make install? |
16:52.53 |
brlcad |
might as well make; make install |
16:52.56 |
brlcad |
just don't make clean ;) |
16:57.12 |
Nidhoggr |
something wacked out and I biffed dir and
untarred again. re-running perl command, etc. |
17:39.54 |
Nidhoggr |
wow. make install takes almost as long as
make. :) |
17:43.59 |
brlcad |
yep |
17:44.19 |
brlcad |
gets fun when I compile on the altix and it
takes only 2 minutes to compile |
17:44.42 |
Nidhoggr |
now how do I check out what it can do?
:) |
17:44.43 |
brlcad |
yet make install takes like 5 minutes .. make
clean takes seemingly forever too |
17:44.57 |
Nidhoggr |
nod |
17:45.08 |
brlcad |
http://brlcad.org Documents section .. the
overview and then intro to mged are good places to start |
17:45.27 |
Nidhoggr |
cool. |
17:47.41 |
*** join/#brlcad Pimpinulla
(~frank@p508215A4.dip0.t-ipconnect.de) |
17:59.51 |
brlcad |
hello Pimpinulla |
18:00.03 |
Pimpinulla |
hey |
18:00.19 |
Pimpinulla |
what was brl-cad's license before? |
18:01.34 |
Pimpinulla |
looks interesting, never heard of it
before |
18:01.42 |
brlcad |
it's actually always been fairly
open |
18:02.05 |
brlcad |
you could get the sourcecode or binaries and
make your own modifications |
18:02.10 |
brlcad |
very gplesque |
18:02.33 |
brlcad |
but .. you had to fill out an agreement form,
fax/mail it back in and wait for a license "key" |
18:02.39 |
Pimpinulla |
i always wondered about the origin of your
nick ;) |
18:02.51 |
Pimpinulla |
ic |
18:02.55 |
brlcad |
that "key" was a decryption key that allowed
you to decrypt and install |
18:03.12 |
brlcad |
and the filing paperwork usually took a week
or two |
18:03.24 |
Nidhoggr |
just ran the bench stuff. kinda
fun. |
18:03.27 |
brlcad |
international requests had to go through
security screenings, etc |
18:03.29 |
Pimpinulla |
is it your project? |
18:03.52 |
brlcad |
i'm one of the maintainers now |
18:03.52 |
Pimpinulla |
oh, some kind of military? |
18:04.13 |
brlcad |
but I didn't start it -- the package has been
around for over 20 years |
18:04.21 |
brlcad |
written by Mike Muuss originally |
18:05.03 |
Pimpinulla |
looks like i have to give it a try
:) |
18:05.05 |
brlcad |
he's the guy that wrote "ping" |
18:05.25 |
Pimpinulla |
oh...well... |
18:05.28 |
brlcad |
as well as ttcp and several aspects of the
original tcp stack and bsd internals |
18:06.09 |
Pimpinulla |
a real pioneer |
18:06.49 |
brlcad |
he was a brilliant man |
18:07.11 |
Pimpinulla |
was... |
18:07.15 |
Pimpinulla |
ic |
18:07.16 |
brlcad |
a real honor to work with .. had a passion for
just about everything he did, very smart |
18:07.33 |
brlcad |
yeah, he died in an accident several years
ago |
18:07.55 |
Pimpinulla |
and you worked with him? |
18:08.39 |
Pimpinulla |
you're not that old yourself, no? not 30 yet
iirc? |
18:09.12 |
brlcad |
i worked with him for about a year |
18:09.37 |
brlcad |
he was the reason I came to work here ..
wanted to be his "apprentice" of sorts |
18:10.10 |
Pimpinella |
where do you work? |
18:10.11 |
brlcad |
as he was one of the few people on the planet
that I'd actually call a wizard |
18:11.37 |
Pimpinella |
there're never enough ppl of that
sore |
18:11.41 |
Pimpinella |
there're never enough ppl of that
sort |
18:14.41 |
Pimpinella |
later |
18:16.36 |
brlcad |
cya |
18:31.29 |
jano |
hmm |
22:06.16 |
starseeker |
preparing to do new ebuild test
now... |
22:07.43 |
*** join/#brlcad tjyang
(~Administr@c-67-175-74-12.client.comcast.net) |
22:20.58 |
starseeker |
and heeeere we go! |
22:47.30 |
brlcad |
weeee.. ;) |
22:47.54 |
starseeker |
stilllll building - nothing outlasts the
brlcad build! |
22:49.30 |
brlcad |
parallel builds are fun ;) |
22:50.00 |
brlcad |
a 12 node altix is the fastest I've seen to
date |
22:50.35 |
brlcad |
compiled in almost exactly 2 minutes with
default options |
22:50.43 |
brlcad |
took longer to install or do a make
clean |
22:52.09 |
brlcad |
altix isn't a cluster, it's smp |
22:52.11 |
starseeker |
build st-build complete ;-) |
22:52.24 |
brlcad |
soo. it worked?! |
22:52.35 |
starseeker |
no no, simulating a build on an altix
;-) |
22:52.45 |
brlcad |
ahh heh |
22:52.51 |
starseeker |
my machine's a wimp by modern standards -
probably another 10 minutes or so yet |
22:53.41 |
brlcad |
autogen.sh takes over two minutes on my fast
home machine |
22:53.53 |
starseeker |
I believe it. |
22:54.37 |
starseeker |
I need to check out a new AMD64+1Gig ram+2
Raptor hard drives |
22:55.03 |
starseeker |
when I get money, of course |
22:55.35 |
starseeker |
BRL-CAD Release 7.0.4, Build
20050126 |
22:55.35 |
starseeker |
Elapsed compilation time: 29 minutes, 52
seconds |
22:55.35 |
starseeker |
Elapsed time since configuration: 31 minutes,
17 seconds |
22:55.41 |
starseeker |
now the moment of truth... |
22:57.45 |
starseeker |
Did you see the announcements? OpenSolaris is
coming, and EROS is now Coyotos |
22:57.52 |
brlcad |
yep |
22:58.26 |
brlcad |
most isn't |
22:58.44 |
brlcad |
we were _very_ close to going with a different
OSI-approved license |
22:58.51 |
brlcad |
that would have been non-gpl
compatible |
22:59.07 |
starseeker |
True, but can you imagine a Solaris with the
strength of the Linux kernel integrated into it? It would change
the face of computing |
22:59.16 |
starseeker |
brlcad: Can't say I blame you |
22:59.34 |
brlcad |
I talked with the gnu legal aids for several
weeks trying to figure out what it would take to make it
compatible |
22:59.46 |
starseeker |
heh - bet that was fun |
22:59.53 |
brlcad |
not really |
23:00.13 |
starseeker |
Tim Daly got so sick of licensing issues
during the Axiom discussions |
23:00.31 |
starseeker |
and some of the most annoying threads in
Maxima history were about our little export laws notice |
23:00.50 |
starseeker |
The problem is, it IS that important. Lawyers
rule the world :-( |
23:00.57 |
brlcad |
especially their position that was being
taken.. very much "if it's not gnu, it shouldn't be used"
regardless of the fact that at the time we could NOT use the
gpl |
23:01.24 |
brlcad |
the gpl is going nowhere in government because
it's a license that's based on copyright law |
23:01.39 |
starseeker |
Yes, they basically piss off everyone who
isn't one of the faithful |
23:01.45 |
brlcad |
the government cannot claim copyright on their
works, they can only be assigned copyright |
23:01.57 |
starseeker |
Oh, good point. |
23:02.16 |
starseeker |
But if they can't claim copyright, doesn't
that make them public domain? |
23:02.27 |
starseeker |
except where export restrictions come into
play? |
23:02.30 |
brlcad |
not in the least |
23:02.45 |
starseeker |
weird |
23:03.04 |
brlcad |
they can still be confidential, unreleaseable,
limited distribution, or under contract |
23:03.20 |
brlcad |
take brl-cad's old agreement for
example |
23:03.28 |
brlcad |
it was technically a contractual
agreement |
23:03.35 |
starseeker |
Hmm. Good point |
23:03.45 |
brlcad |
the osi-approved NOSA is a contractual
agreement |
23:04.00 |
brlcad |
it's the first osi-approved license that is
based on contract law instead of copyright law |
23:04.23 |
starseeker |
Ah. But I suppose that fact itself makes it
GPL incompatible? |
23:04.30 |
brlcad |
which is exactly why NASA made it.. they
couldn't use the gnu licenses without extreme difficulty and in
some cases impossibilities |
23:05.02 |
brlcad |
no it doesn't .. the incompatibility has to do
with subtleties in the redistribution requirements |
23:05.11 |
starseeker |
ah |
23:05.32 |
brlcad |
heh |
23:05.34 |
starseeker |
no wonder you didn't like talking to GNU -
they're the DEFINITION of anal retentive when it comes to stuff
like that |
23:05.43 |
starseeker |
SUCCESS - NO SANDBOX ERRORS!!!! |
23:05.52 |
brlcad |
WOOT! |
23:05.56 |
brlcad |
~starseeker++ |
23:06.23 |
brlcad |
excellent.. then i'll post up a 7.0.4-2
tonight |
23:07.29 |
brlcad |
i didn't mind talking to gnu folks.. but they
weren't very helpful in our situation |
23:08.02 |
starseeker |
I which they'd get used to that situation -
there are many incredible tools that the government could relase if
it were so inclined |
23:08.23 |
starseeker |
mged starts up - what's a good test to run to
make sure this sucker's working? |
23:08.39 |
brlcad |
heh, if mged started, that's a pretty big
test |
23:09.15 |
starseeker |
Will I need to leave the running of autogen.sh
in the ebuild, or will the tarball be ready for
configure? |
23:09.15 |
brlcad |
mm.. can try to open one of the .g files in
db/ |
23:09.19 |
brlcad |
and raytrace it |
23:09.32 |
brlcad |
the tarball will be ready for
configure |
23:10.01 |
starseeker |
let's see where the db dir went... |
23:10.35 |
starseeker |
hmm - not installed apparently |
23:10.44 |
starseeker |
no matter - where's that cvs dir? |
23:11.47 |
starseeker |
I don't see any .g files in db/ are they
generated in the build? |
23:13.06 |
brlcad |
db is not installed |
23:13.29 |
brlcad |
the .g's are made during make |
23:14.00 |
brlcad |
if not, you can "asc2g havoc.asc
havoc.g" |
23:14.09 |
brlcad |
that will convert it |
23:14.17 |
brlcad |
moss.asc is nice and simple |
23:14.31 |
brlcad |
havoc is mildly detailed enough to be
interesting |
23:15.06 |
starseeker |
ok, here we go... |
23:15.59 |
starseeker |
it opened - a helicopter? |
23:16.06 |
starseeker |
how do I raytrace? |
23:16.49 |
starseeker |
hmm |
23:17.09 |
starseeker |
brlcad: should there be a picture by default
in the Graphics Window when I open this file? |
23:18.15 |
brlcad |
nope |
23:19.03 |
starseeker |
Well, I got something that looks like a
helicopter - how do I tell it to raytrace? |
23:19.32 |
starseeker |
Oh, nevermind |
23:20.03 |
starseeker |
somehow, by accident, I got something. But
when I clicked the dismiss button on the raytracer before the
render was done, things froze |
23:22.12 |
brlcad |
there's a raytrace control panel |
23:22.16 |
starseeker |
otherwise, it's WORKING!!! WOOT! |
23:22.17 |
brlcad |
on file, iirc |
23:22.23 |
starseeker |
found it :) |
23:22.29 |
brlcad |
yeah, it's working ;) excellent |
23:22.48 |
Nidhoggr |
yeah.. I changed a drawing, and re-ran
raytrace, and it locked up the process. :) |
23:23.01 |
tjyang |
brlcad, is your solaris box back online
? |
23:24.06 |
brlcad |
tjyang: it was a hardware failure .. it'll be
a while |
23:24.11 |
starseeker |
brlcad - what are you going to call the
tarball? |
23:24.24 |
starseeker |
brlcad-7.0.4-r2.tar.bz2? |
23:24.36 |
jano |
let's call it hubert |
23:24.39 |
starseeker |
brlcad-7.0.4-2.tar.bz2? |
23:24.44 |
jano |
hubert.tarball |
23:24.45 |
jano |
:) |
23:24.54 |
starseeker |
Nah, I'd cut it down to bert |
23:25.06 |
starseeker |
bert the cad |
23:25.22 |
brlcad |
tjyang: pastebin the sys_errlist error, and I
can try a fix here in the meantime |
23:25.42 |
brlcad |
with a coupling cam package called
ernie |
23:26.23 |
tjyang |
brlcad, I will try to find ther error
message. |
23:26.56 |
brlcad |
starseeker: not sure.. good question |
23:29.31 |
brlcad |
starseeker: probably the latter
brlcad-7.0.4-2.tar.bz2 |
23:30.19 |
brlcad |
although sf stats are down |
23:30.23 |
brlcad |
so might just replace existing |
23:31.06 |
*** join/#brlcad tjyang
(~Administr@c-67-175-74-12.client.comcast.net) |
23:35.24 |
tjyang |
brlcad, I have the error message when
compiling into.c on solaris using gcc. what should I do now ? can
post a few lines here ? |
23:36.04 |
starseeker |
brlcad - if you can do that, it would be
easiest |
23:36.42 |
starseeker |
althought I told the gentoo bug it would be
revision two, so if you change the 7.0.4 tarball out let me know
and I'll fix it |
23:43.13 |
tjyang |
brlcad, while waiting your response, I googled
around with the error message and found this link "http://www.radiance-online.org/pipermail/radiance-general/2002-June/000283.html" |
23:48.08 |
*** join/#brlcad guu
(guu@myth.gibbscam.com) |
23:49.15 |
*** join/#brlcad brlcad
(~brlcad@bz.bzflag.bz) |
23:50.42 |
tjyang |
brlcad, do you still need the error message
from into.c ? |
23:55.52 |
tjyang |
into.c compiled fine on rh linux but in rh
linux /usr/include/bit/sys_errlist.h it says "/* sys_errlist and
sys_nerr are deprecated. Use strerror instead. */" |
23:58.31 |
brlcad |
being deprecated is fine.. that's a
warning |
23:58.41 |
brlcad |
you saw an actual error, though? |
23:59.14 |
tjyang |
yes, I still have the log |