On Fri, Sep 07, 2001 at 09:27:33PM -0700, H . J . Lu wrote:
> On Fri, Sep 07, 2001 at 09:19:08PM -0700, H . J . Lu wrote:
> > On Sat, Sep 08, 2001 at 12:14:49AM -0400, Jack Howarth wrote:
> > > howarth@bogus:~$ gcc -v
> > > Reading specs from /usr/lib/gcc-lib/powerpc-linux/2.95.4/specs
> > > gcc version 2.95.4 20010902 (Debian prerelease)
> > >
> > > *libgcc:
> > > libgcc.a%s
> > >
> >
> > It looks like gcc is ok and libtool is broken. Please try to change to
> >
> > *libgcc:
> > -lgcc
> >
> > in /usr/lib/gcc-lib/powerpc-linux/2.95.4/specs. libtool may not know
> > how to deal with libgcc.a%s. On the other hand, I don't know why ppc
> > uses `libgcc.a%s' instead of `-lgcc' to begin with.
> >
>
> Gcc on some platforms uses `libgcc.a%s' instead of `-lgcc'. Does
> libtool know how to deal with libgcc.a%s? It seems that libtool
> drops `libgcc.a%s' for the linking.
It doesn't really know about either, it doesn't look at spec files at
all.
Libtool does nothing more than link with $CC when it is know to work,
or else $LD if it proves to be necessary. The one wrinkle in this
formula is that when CC=gcc, libtool will try a dummy link to
determine whether `-lc' is implicitly added when the link phase is
handled by gcc.
It seems as though libtool needs to do more. Unfortunately my
knowledge of linkers and loaders is superficial, so you will need to
explain what it is that libtool is (or isn't) doing, and what you
would have expected libtool to do (or not do) in painstaking detail in
order for me to get a good grasp of what I can do to fix it :-(
Cheers,
Gary.
--
())_. Gary V. Vaughan gary@(oranda.demon.co.uk|gnu.org)
( '/ Research Scientist http://www.oranda.demon.co.uk ,_())____
/ )= GNU Hacker http://www.gnu.org/software/libtool \' `&
`(_~)_ Tech' Author http://sources.redhat.com/autobook =`---d__/
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
