On Feb 13, 10:26 am, Bill Hart <[email protected]> wrote: > It may be possible, but it requires fundamentally changing the way gcc > works, with respect to libgcc. > > Are you *sure* that blastwave didn't required LD_LIBRARY_PATH to be > set too and you just didn't notice because no binary you built > actually required libgcc?
If you look on the gcc-help list, there is a comment from Dennis Clark, the directory of Blastwave, something like "I would not use LD_LIBRARY_PATH unless someone held a taser at my head". Neither does the gcc from Sunfreewave need LD_LIBRARY_PATH set, though that does install in /usr/local, which might be handled a bit differently by gcc than /opt/csw where Blastwave installs its files. So to the best of my knowledge, it is feasible to get around this, but exactly how is not so clear. I would have thoght that given Blastwave has been around for many years, it would have been discovered if there was something fundamentally wrong with the way they build gcc, as others would have reported the issue. But stranger things have happened. Dave -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
