public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Does libtool know how to deal with libgcc.a%s?
       [not found]   ` <20010907211908.A32493@lucon.org>
@ 2001-09-07 21:27     ` H . J . Lu
  2001-09-10 15:05       ` Gary V. Vaughan
  0 siblings, 1 reply; 2+ messages in thread
From: H . J . Lu @ 2001-09-07 21:27 UTC (permalink / raw)
  To: Jack Howarth; +Cc: libtool, gcc

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.


H.J.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Does libtool know how to deal with libgcc.a%s?
  2001-09-07 21:27     ` Does libtool know how to deal with libgcc.a%s? H . J . Lu
@ 2001-09-10 15:05       ` Gary V. Vaughan
  0 siblings, 0 replies; 2+ messages in thread
From: Gary V. Vaughan @ 2001-09-10 15:05 UTC (permalink / raw)
  To: H . J . Lu; +Cc: Jack Howarth, libtool, gcc

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__/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-09-10 15:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <200109080353.XAA56757@nitro.med.uc.edu>
     [not found] ` <200109080414.AAA31247@nitro.med.uc.edu>
     [not found]   ` <20010907211908.A32493@lucon.org>
2001-09-07 21:27     ` Does libtool know how to deal with libgcc.a%s? H . J . Lu
2001-09-10 15:05       ` Gary V. Vaughan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).