On 25/08/2008, Christopher Sean Morrison <[EMAIL PROTECTED]> wrote: > Outstanding! Now that is some nice debugging -- really, way to go and > thanks! Sounds like you pin-pointed the problem exactly and it all makes > complete sense now including why I haven't run into the problem. (I don't > have a single x86-based system that doesn't support SSE.) >
Thank you. Although I'm a complete newcomer to BRL-CAD, I treated this as I would any other program debugging problem. There's also the fact that I tend to be of the mindset of not wanting to leave an unsolved problem (eg: "Why is this program crashing ?") until I get an answer. :-) > It also explains the relatively recent nature of the invalid instruction > reports as they correspond with the development of NURBS support which is > the only reason configure is adding those flags. The NURBS implementation > can optionally use SSE for fast surface evaluation but that is all > experimental/active development that isn't exposed anywhere else. > > Since it is entirely isolated within the NURBS evaluation and isn't even > critical there, it's completely safe (and recommended) to simply comment out > those related portions of our configure.ac file without any downside. In > fact, I've done this on the latest SVN trunk sources for now until a proper > run-time test can be added to test for SSE functionality. > > As for needing to run make install before make test is rather dependent on > your linker, system, and compilation options. Our tests do usually run > prior to install but that is heavily dependent on libtool doing its job and > our bwish/btclsh automatic auto_path searching. The bwish/btclsh tools scan > the expected source directories for the scripts they're looking for (so that > you specifically don't have to set [I]TCL_LIBRARY and don't have to install) > but a lot of factors come into play as to whether that succeeds. Since the > tests are predominantly for devs, it's been "good enough". The main user > 'tests' are to run 'make benchmark' prior to install (or just 'benchmark' > after install) and to run 'mged' after install. > Ah, the "wonders" of libtool. :-) Yes, that does make sense. > Thanks again for tracking down that problem! That would have been really > very hard to reproduce, isolate, and fix anytime soon. > You are welcome. Simon. -- Simon Clubley [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ BRL-CAD Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-users
