You can't get around requiring LD_LIBRARY_PATH to be set on Solaris Sparc. similarly for LD_LIBRARY_PATH_64. The libgcc is required by some binaries gcc generates, and your linker has to be able to find it. After all, you could have put it anywhere and the linker doesn't have any guidelines on where to look!
You can also set an rpath when building, but that is essentially equivalent. Bill. On Feb 12, 9:00 am, "Dr. David Kirkby" <[email protected]> wrote: > Fran ois Bissey wrote: > > On Fri, 12 Feb 2010 15:29:22 Dr. David Kirkby wrote: > >> I've tried to build sage-4.3.2 on Solaris 10 using gcc 4.4.3 (the latest > >> version). It is complaining about some code in NTL, specicially the use of > >> 'if' and 'define' include/NTL/config.h. > > >> I'm not a C++ programmer. It is normal to put 'if' and 'define' on two > >> lines like this below? > > >> #if /* This is line 57, the first errror */ > >> #define NTL_STD_CXX > > >> I know in C, I'd use > > >> #ifdef NTL_STD_CXX > > >> But perhaps C++ is supposed to permit this. Anyway, for whatever reason, > >> gcc 4.4.3 on Solaris will not accept this - see below. But it does not > >> seem to find iostream.h, which might be a result of, or a cause of the > >> error. > > >> Any thoughts you C++ programmers? > > > Hi Dave, > > > Not really a C++ programmer but I just did a test compile of ntl on my > > system with a shiny new gcc-4.4.3. It worked but after checking what > > I compiled is ntl-5.5.2 not ntl-5.4.2 as in sage. > > Now in 5.5.2 we have this in include/NTL/config.h : > > > #if 1 > > #define NTL_STD_CXX > > > Noticed the "1"? It is very strange as it will always be true, why put "#if" > > at all? > > > Francois > > There is something quite broke on this system I can see, as there are numerous > errors that the system failed to find libgcc_so. Perhaps that file is > dynamically generated, and since the build system on this is screwered up in > some way, that is the source of the problem. Perhaps on some systems that 'if > 1' > becomes on an 'if 0'. > > I'd tried to build gcc in a way that did not require setting of > LD_LIBRARY_PATH. > I thought this had worked ok, as gcc built without any problems, but something > is clearly amiss. > > Back to the drawing board! > > 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
