Well, the FSF gcc is explicitly not supported, that is why the check for Apple.
I assumed (obviously wrongly) that you were using Apple's gcc-3.3 from darwin cvs 1314


Because of the way things are set up, adding fsf gcc support is essentially adding a completely different compiler. Depending on my available free time, I may decide to revisit this issue, do you really think it is required?

Something must be wrong however, I thought it would be reporting that shared libraries are not supported by fsf's gcc. I'll certainly look into that problem.

Thanks,
Peter



On Saturday, May 31, 2003, at 08:22 AM, Bill Northcott wrote:

Another member of our group suggested:
Before installing libtool 1.5, go through the libtool.m4 and change all
the stuff
that says:
if $CC -v 2>&1 | grep 'Apple' >/dev/null ; then \
to:
if true; then
Then rerun libtool's `bootstrap', and reisntall.
The basic problem is that libtool uses the info from "gcc -v" to do
Darwin things if it sees "Apple". GCC 3.3 doesn't report "Apple".

This sounds very plausible to me. It would explain why I have not had trouble building other gnu tools using Apple's compiler. I will test it and report back before sending the complete log.



_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

Reply via email to