IRC log for #brlcad on 20070423

00:22.47 ``Erik I hate to say it
00:23.15 ``Erik but things like that make me think that kevin braunsdorf (ksb@purdue.edu) may've had a bit of a point with his genration utility :(
00:27.08 brlcad genration utility?
01:00.25 IriX64 http://www.pastebin.ca/453474 <--- this is in tk configure but tcl does it too
01:03.06 brlcad any warnings from tcl and/or tk are not our concern
01:03.15 brlcad we just run what they provide
01:03.24 IriX64 whup sorry then
01:03.49 IriX64 problem is your stuff depends on it
01:05.11 brlcad so report the issue to the tcl folks
01:05.29 brlcad they'll probably tell you it's just a warning and wonder wth you're worrying about it
01:05.38 IriX64 they'd laugh at my system
01:06.06 IriX64 but as you say just a warning
01:13.00 CIA-14 BRL-CAD: 03johnranderson * 10brlcad/TODO: updated missing manual pages list
01:15.33 brlcad heh
01:20.51 CIA-14 BRL-CAD: 03brlcad * 10brlcad/TODO:
01:20.51 CIA-14 BRL-CAD: probably don't need to worry about the scripts that retain a script suffix as
01:20.51 CIA-14 BRL-CAD: they're generally utility scripts that aren't as critical. anything that's
01:20.51 CIA-14 BRL-CAD: going to be kept long term should probably drop the suffix on install (like
01:20.51 CIA-14 BRL-CAD: archer, benchmark, brlman, etc)
03:03.29 *** join/#brlcad IriX64_ (n=IriX64@bas2-sudbury98-1096601189.dsl.bell.ca)
07:21.11 *** join/#brlcad clock_ (n=clock@zux221-122-143.adsl.green.ch)
07:53.28 *** join/#brlcad clock_ (n=clock@zux221-122-143.adsl.green.ch)
12:16.14 ``Erik brlcad: "mkcmd", second thing on http://www.npcguild.org/software/pundits/
12:27.47 *** join/#brlcad dli_ (n=dli@adsl-75-33-242-228.dsl.chcgil.sbcglobal.net)
13:09.38 *** join/#brlcad cad06 (n=56692689@bz.bzflag.bz)
13:23.38 joevalleyfield beware the nuke plant
13:25.15 *** join/#brlcad smallfoot- (i=vc@clamwin/translator/smallfoot)
13:30.58 CIA-14 BRL-CAD: 03joevalleyfield * 10brlcad/ (22 files in 7 dirs): (log message trimmed)
13:30.58 CIA-14 BRL-CAD: preliminary support for unaccelerated mgen on aqua through dm-tk
13:30.58 CIA-14 BRL-CAD: configure.ac:
13:30.58 CIA-14 BRL-CAD: - use two levels of expansion for BRLCAD_DATA
13:30.58 CIA-14 BRL-CAD: - enable_aqua configure option
13:30.58 CIA-14 BRL-CAD: - move X11 ac_ macro tests from argument check section
13:31.00 CIA-14 BRL-CAD: - rely on AC_PATH_XTRA to figure out most of what we need to know about
14:40.04 brlcad heh "In fact it might be bad. I wouldn't recommend that you download it or run any part of it. Just read it."
14:40.59 joevalleyfield sounds like a certain opengl tutorial
14:52.21 *** join/#brlcad Elperion (n=Elperion@p548754A5.dip.t-dialin.net)
15:17.12 *** join/#brlcad clock_ (n=clock@zux221-122-143.adsl.green.ch)
15:37.23 ``Erik certain ogl tutorial? nehe isn't even worth reading, it's as damaging to ogl programming as basic is to programming in general O.o *duck*
15:38.02 joevalleyfield and he readily admits it
15:40.53 ``Erik well, he admits that he isn't a guru
15:41.31 ``Erik uhhh, there's history there. the #opengl channel on efnet and nehe have... butted heads. and when he stole brinks tga loading code (verbatim) and claimed he wrote it, wooo, we got spun up :)
15:41.42 ``Erik he closed his site for a few weeks after that, but came back
15:44.16 joevalleyfield interesting
17:09.46 *** join/#brlcad clock_ (n=clock@zux221-122-143.adsl.green.ch)
18:05.05 *** join/#brlcad IriX64 (n=IriX64@bas2-sudbury98-1096601189.dsl.bell.ca)
18:17.20 IriX64 http://www.pastebin.ca/454580 <--- could use some help here on my system "x" fails the test.
19:33.05 IriX64 http://irix32.spaces.live.com/photos <--- new wall candy, finally got it going.
19:38.09 IriX64 http://irix32.spaces.live.com/photos/work is easier
19:45.44 IriX64 graphics is graphics, back to 7.10.1.
19:49.49 IriX64 mc
19:49.56 IriX64 your pardon.
19:53.08 brlcad need to see why it failed, not snippets from configure.ac
19:53.20 brlcad look in config.log, find the X11 test that failed
19:53.49 brlcad you can look for the AC_MSG_CHECKING statements in the config.log to find things
19:53.55 IriX64 already fixed thankyou.
19:54.16 brlcad and how was it fixed?
19:54.39 IriX64 i patched it.
19:54.49 brlcad patched what?
19:55.01 IriX64 that prefix thing.
19:55.24 brlcad do you not remember what was said just two days ago?
19:55.34 brlcad "--with-x11" is wrong
19:55.48 IriX64 actually i don't i was just looking for help.
19:56.07 IriX64 X is all i have
19:56.08 IriX64 .
19:56.09 brlcad i'm trying to help, but you're bringing up the exact same issue
19:56.27 brlcad and i told you what to do about it already
19:56.46 IriX64 leaving ---with-x out is no solution
19:56.51 IriX64 err --
19:57.28 brlcad adding it isn't a solution either
19:57.45 brlcad it's only if it's no that it'll turn it off, and it is not no by default
19:58.21 IriX64 but i'm *trying to get an X11 build going here
19:58.28 brlcad i understand that
19:58.38 brlcad using --with-x11 doesn't help you AT ALL towards that goal
19:58.47 brlcad it actually just makes it worse
19:58.55 brlcad because that's not how that option is supposed to be used
19:59.02 brlcad it's supposed to be a path
19:59.07 brlcad it's not an on/off option
20:01.07 IriX64 noted
20:11.02 *** join/#brlcad clock_ (i=clock@84-72-60-151.dclient.hispeed.ch)
20:19.54 IriX64 http://irix32.spaces.live.com/photos/work
20:25.20 *** join/#brlcad poolio (n=poolio@adsl-70-130-226-251.dsl.stlsmo.swbell.net)
20:27.35 IriX64 lets say i've done some work on for instance, mged.tcl and you've done a commit of the same file after i've done my work, what happens on a cvs update?
20:29.10 joevalleyfield it helps you merge
20:29.31 IriX64 really , no need to save and hack?
20:29.38 joevalleyfield no
20:29.49 joevalleyfield if you modified the same lines as the committer,
20:30.04 joevalleyfield there will be a "conflict" for you to resolve
20:30.13 IriX64 noted and thanks
20:30.36 joevalleyfield your modifications will still be in the file though-- it won't delete your stuff
20:31.06 IriX64 thanks.
20:31.41 ``Erik 'cept hte modifications will be, um, modified :D
20:31.45 IriX64 :)
20:32.02 ``Erik cvs is pretty non-destructive, even if you tell it to be destructive (like the AC flags), it'll save the "local" copy to .#file.revision
20:32.30 IriX64 hope my client is up to snuff
20:32.44 IriX64 :)
20:33.01 ``Erik which are you using? the cygwin cvs is the same one we all use on unix
20:33.08 ``Erik wincvs mgiht be different
20:33.09 IriX64 thats it
20:33.17 IriX64 no the cyg one
20:33.25 IriX64 is being used here
20:33.32 ``Erik then it's up to snuff. It's the benchmark all others strive to be. :)
20:39.49 *** join/#brlcad Elperion (n=Elperion@p548754A5.dip.t-dialin.net)
20:41.20 IriX64 question: I made some mods to the cygwin dll's to get this to run with Xming and Xwin32, and it works for winaxepro too, trying to be universal here, who elses windows xserver should i test with?
21:02.36 IriX64 forgive me, forgot what channel i'm in :)
21:31.15 *** join/#brlcad Twingy (n=justin@74.92.144.217)
22:26.54 *** join/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1178015006.dsl.bell.ca)
22:28.31 IriX64 missed the answer to my question, any decent gnu or free xserver for windows platforms out there?
22:43.57 IriX64 http://irix32.spaces.live.com/photos/work
22:44.03 IriX64 this is with xming
22:44.15 IriX64 thinking of putting it in the package
22:45.06 IriX64 exec fbserv 2 /dev/X also works.
22:46.09 IriX64 that version 9.9.9 was just a test.
22:52.46 IriX64 oh joy i now have three frame buffers active.
22:54.13 IriX64 I think XMing is going to be it, I like their price.
23:26.19 IriX64 if you start a console session in windows land, and type path=c:\usr\brlcad, thats all that's needed (and you have to have brought up X too though), starting it from the desktop requires the path be set properly in system land sigh.
23:26.46 IriX64 err brlcad\bin
23:27.38 IriX64 dopped the dll's in bin, works for me.
23:27.50 IriX64 dropped too
23:36.54 IriX64 http://irix32.spaces.live.com/photos/work (Both frame buffers active)

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