[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Solaris 9 + gcc

From: Bob Friesenhahn
Subject: Re: Solaris 9 + gcc
Date: Fri, 10 Dec 2004 10:00:32 -0600 (CST)

On Fri, 10 Dec 2004, Ralf Wildenhues wrote:

My guess: libtool variable sys_lib_dlsearch_path_spec contains
/usr/local/lib, but the dynamic linker does not search it?
The problem does not go away after using `crle'?  The configuration for
crle does not contain /usr/local/lib as trusted directory?
(Why does libtool not use crle BTW?)

Using crle to obtain information seems fine to me, but libtool should definitely not adjust system settings using it.

You are not the first one to report problems with libgcc on Solaris.
I don't feel too qualified to work on this, because I don't have access
to it and never used it before.  I'm not sure what the real problem is
in this case.  Help wanted (the libtool maintainer crew is understaffed

I suggest that either the user add -R/usr/local/lib, use crle to cause the system to look there by default, or perhaps even use LD_LIBRARY_PATH (not recommended).

On my own system, I install GCC with the --enable-version-specific-runtime-libs option. I use crle to tell the system to look in /usr/local/lib, but then I add symbolic links in /usr/local/lib which point to the installed compiler libraries so they are found at run-time.

I don't think there is much technical difference between Linux and Solaris in this regard. With Linux, GCC is part of the system so libgcc is installed where it is always found. With Solaris, libgcc is often installed to a non-system directory so it is not found by default.

Bob Friesenhahn

reply via email to

[Prev in Thread] Current Thread [Next in Thread]