IRC log for #brlcad on 20070623

00:16.17IriX64http://rafb.net/p/oynrsY45.html just curious, have i hit solaris code yet?
00:19.09IriX64remember i ignore warnings such as cast make integer from pointer of different size
00:19.43IriX64because in a cast i assume you know what you want
00:36.47IriX64http://rafb.net/p/UZsUZI80.html   <---- is anybody else getting this kind of stuff, this is trying to make bwish
00:37.35IriX64reams of errors do you want all of it?
00:40.25IriX64http://rafb.net/p/D4wdlm67.html maybe that will help
00:41.45IriX64bte mged exhibits the same symptom, i tried compiling it just in its directory
00:41.51IriX64btw too
01:15.52*** join/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1096601029.dsl.bell.ca)
02:04.09*** join/#brlcad cad46 (n=4b139e8d@bz.bzflag.bz)
03:37.15*** join/#brlcad Twingy (n=justin@74.92.144.217)
05:59.45*** join/#brlcad Laniakea (i=clock@77-56-107-241.dclient.hispeed.ch)
08:21.50*** join/#brlcad Elperion (n=Bary@p54876820.dip.t-dialin.net)
09:36.23*** join/#brlcad deltazap (n=deltazap@pool-71-251-104-132.tampfl.fios.verizon.net)
12:49.18*** join/#brlcad elite01 (n=elite01@dslc-082-082-068-204.pools.arcor-ip.net)
13:26.33*** join/#brlcad CIA-4 (n=CIA@208.69.182.149)
13:43.12*** join/#brlcad CIA-4 (n=CIA@208.69.182.149)
14:54.42*** join/#brlcad Laniakea (i=clock@77-56-107-241.dclient.hispeed.ch)
15:28.57*** join/#brlcad Laniakea (i=clock@77-56-107-241.dclient.hispeed.ch)
16:49.56*** join/#brlcad Laniakea (i=clock@77-56-107-241.dclient.hispeed.ch)
17:01.28*** join/#brlcad docelic (n=docelic@212.15.179.73)
17:02.12*** join/#brlcad CIA-4 (n=CIA@208.69.182.149)
17:22.54*** join/#brlcad CIA-4 (n=CIA@208.69.182.149)
18:09.08*** join/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1096601029.dsl.bell.ca)
18:17.14IriX64http://irix32.spaces.live.com/photos brlcad albumn, here's that photoshop pix of tinwoodsman i promised you :P
18:28.52IriX64actually it's a 5-clicks photo ;)
18:30.11IriX64brlcad: i deleted that tree and did a fresh complete cvs checkout, waiting on you now at your leisure.
18:31.57poolioIriX64: It's the weekend, he might not be working today :)
18:33.05IriX64doh!!!! yer right
18:34.11IriX64you get that iceweasel of yours to access the blog?
18:34.52IriX64heh firefox detected refusing access()
18:35.57IriX64probably hides on weekends :)
18:37.14poolioIriX64: no, i haven't bothered though, been busy with work/play.
18:37.43IriX64ahh
18:38.13IriX64wonder if others have that problem, i know yukonbob hit it too
18:38.33IriX64said something about curling the url
18:41.28IriX64http://rafb.net/p/FDzKcw22.html   hehe checking the solaris code :)
18:44.13IriX64understand how this works, I can follow any of the lines you support and cross compile to my platform :)
18:57.28*** join/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1096601029.dsl.bell.ca)
18:59.14IriX64yukonbob, he fixed your display thing , fisheye :)
18:59.23IriX64errr check fisheye
19:07.41*** join/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1096601029.dsl.bell.ca)
19:13.09IriX64heh
19:13.38IriX64only thing i don't like is defaults to join on open
19:18.06IriX64my irix32 blog :)
19:22.11IriX64should have put the pirates of the carribean up at disney
19:49.22*** join/#brlcad neur0n (n=andreas@52.81-167-60.customer.lyse.net)
20:28.08*** join/#brlcad CIA-4 (n=CIA@208.69.182.149)
20:48.21*** join/#brlcad Elperion (n=Bary@p54876820.dip.t-dialin.net)
21:39.46IriX64poolio.... that assert.h thing, thought they fixed it.
21:40.45IriX64well i fixed my copy sigh... again
21:41.15IriX64sometimes it doesn't pay to start from scratch :)
21:41.53IriX64scratch being a complete cvs checkout
21:42.09poolioI can commit it for you
21:42.33IriX64could you just #include <assert.h> with his includes
21:42.43poolioyeah sure, one sec
21:42.48IriX64thanks
21:44.07pooliowhich file was it in again?
21:44.23IriX64opennurbs_bezier.cpp
21:45.05IriX64not sure if it should go there or common.h
21:45.38IriX64i put mine in the cpp file
21:46.26IriX64is that file name right just a sec
21:47.21IriX64its right
21:47.27poolioI'm just going to put it in opennurbs_bezier.cpp, the dev can move it later if he wants
21:47.39IriX64good
21:48.10poolioalright, cvsup
21:48.19IriX64thanks
21:48.37CIA-4BRL-CAD: 03poolio * 10brlcad/src/other/openNURBS/opennurbs_bezier.cpp: included assert.h
21:55.03IriX64http://rafb.net/p/CKliVD10.html    line 3352 or there abouts poolio, why set x11_works to no on a successfull test result?
21:55.22IriX64err configure.ac
21:56.04IriX64the previos check sets to yes, this one resets to no on success
21:58.14IriX64so when i go edit happy, I just change that little no to a yes, and voila my x passes inspection now
21:58.23IriX64heh
22:01.57poolioI ahve a feeling you fail the second check
22:02.19poolioIt doesn't set it to no on success, it sets it to no on failure. And apparently you fail that check
22:06.45pooliohttp://rafb.net/p/vXnvBf74.html
22:06.49pooliocompile and run that and tell me what it outputs
22:08.15IriX64just a sec
22:12.43IriX64undefined reference to _Xnewmodifier map, you telling me my x is broken?
22:12.53poolioyes siree.
22:13.00IriX64crapville
22:13.02pooliooh wait, it won't even compile?
22:13.06IriX64right
22:13.15pooliooh duh
22:13.23poolioyou have to link the right xlibs, one sec
22:15.11poolio-lX11
22:16.07IriX64gives back a pointer so my x is not broken :)
22:16.23IriX64you printfed the pointer its there poolio
22:17.12IriX64IriX64@FthrNtr ~
22:17.12IriX64$ ./test
22:17.12IriX640x100f0198
22:17.12IriX64IriX64@FthrNtr ~
22:17.13IriX64$
22:18.58IriX64going for a walk cya later, thanks for the commit
22:19.15poolioIriX64: wait, got another minute?
22:21.49poolioah well, you'll read it when you get back. I don't know much about automake so I missed this, but AC_TRY_RUN has 4 arguments, the first is the program, , if the program  returns true the second argument is executed, false the third, and ** if autoconf knows it is cross-compiling for another
22:21.54pooliomachine and therefore can't run a test program at all, it doesn't try
22:21.57pooliobut just executes the fourth argument.
22:37.50IriX64so what are we saying here i have a busted x11?
22:39.47IriX64so,,x11_works=no what will happen on success
22:40.28IriX64x11_works gets set to a null?
22:41.44IriX64whats wrong with plain ole [x11_works=yes] ?
22:42.39IriX64gotta reboot ill be back
22:42.44*** part/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1096601029.dsl.bell.ca)
22:47.45*** join/#brlcad IriX64 (n=mario_du@bas2-sudbury98-1096601029.dsl.bell.ca)
22:48.03yukonbobIriX64: what "display thing" are you talking about...?
22:48.51IriX64DISPLAY environment variable brlcad did something about it
22:49.01*** join/#brlcad elite01 (n=elite01@dslc-082-082-068-204.pools.arcor-ip.net)
22:49.40IriX64poolio if i change it to just ,[x11_works]   the result is true which means the test passed and i do have that little thing it's testing for
22:49.50IriX64err x11_works=yes
22:50.34yukonbobIriX64: Ahh... ;)
22:53.11IriX64the url for fisheye1 is in the topic if you ewant to look
22:53.17IriX64err want
22:53.26poolioIriX64: Well, I don't think it will execute the ,[x11_works] = yes, it detects you are cross-compiling and doesn't even bother to do AC_TRY_RUN (I think). So for now I'd just hack it apart/comment out/whatever to make it run
22:53.50poolioI don't quite see why that test is being run, it looks like it only is for testing if you are cross compiling
22:53.58IriX64right but one argument is set it to that if true correct?
22:54.17pooliohuh?
22:54.19IriX64only one ,
22:54.39poolioJust comment it out / change it to automatically set x11_works = yes for now, and talk to brlcad when he gets back about why they bother to run that test
22:55.00IriX64good
22:55.45IriX64every time i touch configure.ac he calls me edit happy :P
22:56.50IriX64good to be happy tho, edit or otherwise ;)
22:56.56poolioWell, you are edit happy. There are reasons things are done and checked for in configure.ac and brlcad wants to make sure it compiles and runs on as many systems as possible. So he doens't just wnat to cut out a certain check / modify it so it works for _you_, because that could break the install for many others
22:57.24IriX64you mean nobody else is seeing this?
22:58.31poolioWell, it seems like for some reason or another X11 is automatically disabled if you are cross compiling.(maybe ;))
22:58.41poolioAnd I would presume there is a reason, I just don't know what
22:58.47IriX64mebbe so :)
22:58.53poolioI don't think very many people cross compile brlcad
22:59.21poolio...why are you cross compiling?
23:01.42IriX64oh i see, let me clarify cygwin is not supported, so i follow a code line that is supported and generate code for my system from it
23:02.29IriX64true cross compiling is a ways down the road yet
23:03.08IriX64but already I have grief, most configures bail out saying can't check such and such while cross compiling
23:03.49pooliothat's a bummer. I feel like if you can compile _for_ a system there is no reason why you can't compile _on_ that system
23:04.05IriX64so i cheat and use the build,target,host switches and preprocess configure to provide results based on those.
23:04.57IriX64or on another system is the way i feel about it
23:05.17poolioif you're willing to run cygwin why not just spare yourself a headache and run it in vmware or something
23:05.27IriX64if you're in config.sub, i may support you :)
23:05.46IriX64vmware is costly
23:05.52poolioIt's actually free
23:06.01IriX64since when?
23:06.03poolio(vmware player)
23:06.20IriX64heh thought you meant vmware workstation
23:06.51IriX64i actually have an expired copy on here with warp4 on it
23:06.55pooliono, but if you found someone with vmware workstation and just made an image, you could distribute that image (probalby of a linux install with brl-cad)
23:07.13IriX64?? illegal
23:07.21pooliono, it's entirely legal
23:07.33IriX64how vmware costs money.
23:07.57pooliowell find someone who has bought it and use their computer to do it, or ask brlcad nicely and maybe he could do it. he's got funding :)
23:08.07IriX64:)
23:11.55IriX64see if the BSD or SOLARIS specific stuff successfully builds it means it's working
23:12.28IriX64my latest 7.8.8 had the -DBSD flag set it runs here.

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