%% Dan D Niles <dan_at_more.net> writes:
ddn> This seems to have fixed it. I am using the gcc package from
ddn> www.sunfreeware.com. I guess that package is broken.
Not necessarily.
On Solaris, using the -L option to specify where to find shared
libraries is not enough. That will help the compile-time linker ld(1)
find them, but it won't set the path for the run-time linker ld.so(1) to
find them.
On Solaris, when dealing with shared libraries that appear in
non-standard places, you also must use the -R option to set the run-time
link path.
If your installation of GCC uses a shared stdc++ (standard C runtime)
then you likely will need to add a -R flag to your compile line telling
the linker where to look.
For example, if your compiler installs its shared libraries in
/opt/gcc-2.95.2/lib, then you would do this:
$ cd fvwm-2.2.5
$ make clean
$ rm config.cache
$ LDFLAGS="-R/opt/gcc-2.95.2/lib" ./configure ...
$ make
and that should work.
Whether it's this installation of GCC that is broken or whether it is
this behavior of Solaris that is broken, is an exercise for the reader.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> HASMAT--HA Software Methods & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Jun 25 2001 - 12:14:54 BST