%% Dan D Niles <dan_at_more.net> writes:
ddn> LDFLAGS="-R/usr/local/lib/gcc-lib/i386-pc-solaris2.8/2.95.2" ./configure
ddn> Which has libstdc++.so (a link) but not libstdc++.so.2.10.0. The
ddn> libstdc++.so.2.10.0 file is in /usr/local/lib, but libstdc++.so is
ddn> not.
That is indeed a strange configuration.
ddn> The following did work:
ddn> LDFLAGS="-R/usr/local/lib" ./configure
ddn> Perhaps this could be auto-configured when compiling on x86.
I don't see how configure could really know what the right path would
be.
Anyway, this isn't an x86 issue, it's a Solaris issue. Solaris on SPARC
behaves the same way.
And, finally, if this issue can be resolved it really this issue needs
to be resolved by autoconf itself. Possibly if/when we switch to the
next official autoconf (2.50) in FVWM, this won't be an issue (I don't
know; I haven't tried it--I _do_ know they fixed the cross-compiler
stuff so you won't see the confusing message you did here, but instead
something like "Can't find a working C++ compiler" or similar... because
I, among others, abused the autoconf folks until they changed it :).
ddn> Is this still necessary with the beta version of fvwm?
Maybe. The next release of FVWM doesn't need a C++ compiler at all, so
this particular manifestation doesn't exist.
However, you could run into the same issue with other shared libraries:
say you installed libXpm.so or the stroke or readline or whatever
libraries in directories other than the standard system directories;
then you need to add -R to get the run-time linker to look there as
well.
--
-------------------------------------------------------------------------------
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 - 14:25:38 BST