IRC log for #brlcad on 20071103

00:09.10 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
00:20.00 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
00:27.17 *** join/#brlcad IriX64_ (n=IriX64@bas2-sudbury98-1096601470.dsl.bell.ca)
00:52.46 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
01:03.06 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
01:17.29 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
01:19.15 *** part/#brlcad rpaddock (n=bob_padd@c-24-131-109-50.hsd1.pa.comcast.net)
01:33.47 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
01:55.56 *** join/#brlcad Lucifer (n=satan@ppp-70-243-82-198.dsl.austtx.swbell.net)
01:56.28 Lucifer so, for those of us who are cad-illiterate, is brl-cad a functionally complete replacement for autocad for machines?
01:57.18 *** join/#brlcad ct|kyle (n=kyle@pool-71-97-143-220.aubnin.dsl-w.verizon.net)
02:01.13 IriX64 http://rafb.net/p/YDzIAj85.html <---- this didn't happen last time, dunno why this time
02:02.17 IriX64 must be me, ah well
02:16.49 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
02:19.10 *** join/#brlcad IriX64 (n=mariodot@bas2-sudbury98-1096601470.dsl.bell.ca)
02:26.25 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
04:32.15 *** part/#brlcad ct|kyle (n=kyle@pool-71-97-143-220.aubnin.dsl-w.verizon.net)
08:03.19 *** join/#brlcad minute (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron)
09:46.23 *** join/#brlcad minute (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron)
10:39.23 *** join/#brlcad Elperion (n=Bary@p5487589A.dip.t-dialin.net)
11:01.35 *** join/#brlcad CIA-27 (i=cia@208.69.182.149)
12:00.06 *** join/#brlcad elite01 (n=elite01@dslc-082-082-078-209.pools.arcor-ip.net)
13:37.48 *** join/#brlcad Elperion (n=Bary@p5487589A.dip.t-dialin.net)
14:08.54 *** join/#brlcad rpaddock (n=bob_padd@c-24-131-109-50.hsd1.pa.comcast.net)
17:37.01 *** join/#brlcad yukonbob (n=yukonbob@198.235.198.234)
18:17.46 IriX64 http://rafb.net/p/SoT44O89.html <--- not too familiar with cvs, what's this?
18:19.21 IriX64 bearing in mind i'm starting from scratch
18:24.24 IriX64 can't be too serious i got my checkout :)
18:40.29 IriX64 yukonbob: i tried tcl/tk8.4 and it compiles, but at runtime i get a complaint of needing tcl8.5 :(
18:41.40 IriX64 from itcl that is
18:42.29 IriX64 he say: "so use tcl8.5" ;)
18:42.38 *** join/#brlcad minute (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron)
20:02.08 *** join/#brlcad minute (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron)
20:46.04 *** join/#brlcad Z80-Boy (i=clock@77-56-78-208.dclient.hispeed.ch)
21:24.39 yukonbob IriX64: what generated the error; depending on that, I'd be curious to see your build... I've been using tcl/tk 8.4 and associated libs w/o problems for a while...
21:25.05 IriX64 itcl said it needed 8.5
21:25.27 yukonbob from running mged, I take it?
21:25.36 IriX64 yes
21:25.43 IriX64 on 7.11.0 build
21:28.43 yukonbob well, the itcl/itk binary libs might be (probably are) linked against what they hope are tcl/tk8.5, which is _not_ what you want... I'm running itcl/itk "current (20040920)" built against tcl/tk 8.4 w/o issues
21:29.29 IriX64 I see ... i think you're right in that
21:30.39 IriX64 if I ever get this thing running, I think I'll "freeze" the code tree :)
21:31.58 yukonbob if you build or install itk/itcl the same way you put tcl/tk 8.4 on your system, instead of relying on the brl-cad distributed bits, you'll fare better... make sure you're using the already installed/properly working tcl/tk 8.4, and itcl/itk, w/o building from the brl-cad distributed source. the .tgz ships with _everything_ for completeness' sake, but you're not obligated to build from it -- in fact there are good reasons to _not_ build with it...
21:32.29 IriX64 noted
21:32.42 yukonbob did you use the notes/diffs I posted earlier for modifying the configure.ac, etc?
21:33.10 IriX64 didn't take much fiddling, i'm pretty good at that schtuff
21:34.32 IriX64 hehe stereo compiles, 7.8.4 vs 7.11.0 :)
21:37.24 yukonbob IriX64: re: fiddling -- cool... you might want to compare notes in any event even if you do your own fiddling; the work I've done to date works, and might help you get a working compile too. Then we can compare methods/results once you're up/running...
21:37.44 IriX64 http://www3.sympatico.ca/mario.dulisse2/stereo.png
21:37.55 IriX64 understood yukonbob, thanks
21:49.13 IriX64 err murphy too
21:51.31 *** join/#brlcad elite01 (n=elite01@dslc-082-082-078-209.pools.arcor-ip.net)
22:16.59 *** join/#brlcad rpaddock (n=bob_padd@c-24-131-109-50.hsd1.oh.comcast.net)
22:20.52 *** join/#brlcad b0ef (n=b0ef@062016141081.customer.alfanett.no)
22:27.55 ``Erik um
22:28.30 ``Erik if you build itcl from the brlcad repo and use a system installed tcl, if the system tcl is not the exact same version as the one in src/other/tcl (8.5a6), it will fail
22:29.19 ``Erik the 'easy' way to fix it is to edit the init.tcl script in src/other/tcl/library and around ~20ish lines in, there'll be a "require" line with an "exact version" argument, change the 8.5a6 to your system tcl version
22:30.08 ``Erik the 'real' way to fix it is to make all the itcl stuff, ampi stuff, etc know to use the systems init.tcl instead of the hardcoded path to the included init.tcl
22:30.10 ``Erik :D
22:45.13 IriX64 he says calmly... pffft on that it should just "know" :)
22:47.51 IriX64 i'm tempted to set DON'T_HAVE_CONFIG_H....act accordingly :)
22:51.21 IriX64 mmmmm unlimber 9mm, fire at foot
22:51.47 yukonbob ``Erik: or complete remove the "-exact Tcl [blahblah]", and just use "package require Tcl" and let it pick the best one available...
22:54.03 yukonbob ...or use your systems (or orig. distribution of itcl/itk) and let them sort it out, and manage those things (tcl, tk, itcl, itk, tkimg, etc) seperately, instead of from w/i a big build like "brlcad, incl. tcl, tcl, tkimg, itk, itcl, libpng, liburt, jove, etc., etc.)
22:57.09 ``Erik yeah *shrug* that file is straight from tcl
22:58.15 ``Erik <-- favor of the "let the package maintainer deal with the dependancies" angle
22:58.21 ``Erik in favor of, even
22:58.23 ``Erik *shrug*
22:58.48 ``Erik there are issues with that, though, with version requirements and shtuff
23:09.40 IriX64 http://rafb.net/p/TaNn2860.html <--- someone... this is a prob here, is it a prob elsewhere?
23:16.01 IriX64 wtf is g-nmg, and why is it compiling here ;)
23:19.04 ``Erik a G to NMG converter
23:19.28 IriX64 urfff something else i'll prolly never use :)
23:20.19 IriX64 heh photon mapping is a huge yes :)
23:21.31 IriX64 i checked out today thankyou :)
23:22.46 louipc IriX64: what file is that in?
23:23.08 IriX64 read the description
23:23.27 louipc ah
23:26.38 louipc what's it setting it to?
23:26.50 IriX64 its set to nothing ie ""
23:27.24 IriX64 i manually set it to -L/usr/X11R6/lib, that works on *my system
23:27.31 louipc you should investigate XLIBSW I think
23:27.39 louipc tcl.m4: XLIBSW="-L$i -lX11"
23:28.06 IriX64 louipc it has to be told *where to find X11
23:29.04 louipc aye you have a really odd system too eh? so ./configure might not find it
23:29.20 IriX64 right thats why i said on *my system
23:29.41 louipc is it just cygwin?
23:29.53 louipc or is it a messed up cygwin? hehe
23:29.57 IriX64 thats what i'm asking :)
23:30.05 louipc I dunno I don't use it
23:30.27 louipc you might want to submit a patch or something for it to work with cygwin
23:30.56 IriX64 on the bright side i'm currently at rtserver, a point hitherto unreached before :)
23:31.18 louipc cool
23:31.40 IriX64 louipc: i don't do patches, build from scratch if neccessary ;)
23:32.23 IriX64 afk
23:32.30 louipc why not, your contribution could benefit other cygwin users if it's a standard cygwin setup
23:33.26 IriX64 I have to agree with brlcad, i'm too edit-happy for such
23:33.31 IriX64 :)
23:33.55 louipc looks like a few lines starting at 2411 in tcl.m4 would need adding to
23:34.25 louipc (at line 2411)
23:35.00 louipc heh I don't like to have to edit the same thing more than is necessary (eg. once)
23:36.53 louipc and all your progress might end up for nothing if for example you decide to do something else for awhile and forget what exactly you need to do. :P
23:37.36 yukonbob IriX64: louipc++ -- building patches is where it's at -- _especially_ if you don't like doing it -- since if it's accepted (or used as a basis for improvement) you may never need to do it again ;)
23:38.13 louipc yeah and even if you have a weird ass system, just keep a patch for yourself
23:38.24 louipc untar, patch, configure, make
23:40.01 yukonbob might even help one figure out _why_ a system is weird, and allow to fix problem at root (ie: "unweird" your system ;)
23:40.35 louipc lol
23:42.15 IriX64 forget it i'm not about to build a cygwin firefox, they have a windoze version, use it :)
23:43.19 louipc yeah no point
23:43.33 IriX64 irssi however ;)
23:45.09 IriX64 starting parallel compiles of 7.8.4 and 7.11.0 is an exercise in patience :)
23:45.30 IriX64 but i wanted to see what the system could do
23:46.54 louipc I remember building tcl/tk on mingw that was cool
23:47.35 IriX64 yukonbob:insert diddler, tweak cpu clock to max, back out one quarter turn :)
23:48.32 yukonbob louipc: are you running brl-cad on Windows natively?
23:55.12 IriX64 ``Erik package_require blahblah, if i #package_require blahblah, will it fly?
23:55.26 louipc yukonbob: no I haven't run windows for 4 yrs or so
23:59.22 yukonbob IriX64: no
23:59.39 yukonbob ...and it's "package require", not "package_require"
23:59.52 yukonbob that's a tcl command to load external code.

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.