Paul D. Smith writes:
> %% Dan D Niles <dan_at_more.net> writes:
>
> ddn> That does not work. It still thinks my C++ compiler is a
> ddn> cross-compiler, and breaks during the configure.
>
> You're sure you used the right directory, right? My example was just
> that: an example. I don't have the first idea where these files reside
> on your system. Look in the directory you provided via -R; you should
> see a file libstdc++.so.<some-stuff> there. If not, you don't have the
> right directory.
Odd, I used:
LDFLAGS="-R/usr/local/lib/gcc-lib/i386-pc-solaris2.8/2.95.2" ./configure
Which has libstdc++.so (a link) but not libstdc++.so.2.10.0. The
libstdc++.so.2.10.0 file is in /usr/local/lib, but libstdc++.so is
not. The following did work:
LDFLAGS="-R/usr/local/lib" ./configure
Perhaps this could be auto-configured when compiling on x86. Is
this still necessary with the beta version of fvwm?
Dan
--
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 - 13:51:08 BST