This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: IA64 libc.so always depends on libunwind?

From: David Mosberger <davidm at napali dot hpl dot hp dot com>
To: "H. J. Lu" <hjl at lucon dot org>
Cc: davidm at hpl dot hp dot com, GNU C Library <libc-alpha at sources dot redhat dot com>
Date: Tue, 6 Apr 2004 15:06:01 -0700
Subject: Re: IA64 libc.so always depends on libunwind?
References: <20040406204737.GA7295@lucon.org><16499.6633.259968.828786@napali.hpl.hp.com><20040406215023.GA8340@lucon.org>
Reply-to: davidm at hpl dot hp dot com

>>>>> On Tue, 6 Apr 2004 14:50:23 -0700, "H. J. Lu" <hjl@lucon.org> said:

  >>  I didn't think so.  I thought the unwind-dependencies in glibc
  >> were handled by loading libgcc_s on demand (which has its own
  >> dependency on libunwind, if built against it).

  HJ> libc.so is linked against -lgcc -lgcc_eh -lunwind where libgcc
  HJ> and libgcc_eh are archives.

Perhaps that's OK then.  You could link in a static libunwind, of
course, but I don't think that's the right solution.

	--david

Follow-Ups:
- Re: IA64 libc.so always depends on libunwind?
  - From: H. J. Lu

References:
- IA64 libc.so always depends on libunwind?
  - From: H. J. Lu
- Re: IA64 libc.so always depends on libunwind?
  - From: David Mosberger
- Re: IA64 libc.so always depends on libunwind?
  - From: H. J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]