This is the mail archive of the libc-alpha@sourceware.org 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: Avoid use of libgcc_s and libgcc_eh when building glibc

From: Thomas Schwinge <thomas at codesourcery dot com>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: libc-alpha at sourceware dot org, Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>, Roland McGrath <roland at hack dot frob dot com>
Date: Wed, 30 May 2012 23:51:35 +0200
Subject: Re: Avoid use of libgcc_s and libgcc_eh when building glibc
References: <Pine.LNX.4.64.1205282140020.2726@digraph.polyomino.org.uk> <20120529235232.E0F742C0B8@topped-with-meat.com> <Pine.LNX.4.64.1205301052380.25659@digraph.polyomino.org.uk>

Hi!

On Wed, 30 May 2012 10:59:46 +0000, "Joseph S. Myers" <joseph@codesourcery.com> wrote:
> I'd like architecture maintainers to test this, for all libc architectures 

I've done a regular (that is, non-bootstrap) cross-build for SH; no
issues found.

> (Hurd testing would be good as well if possible.)

I'll give it a shoot when I'm back next week.  I can also easily do a
bootstrap cross-build there.

GrÃÃe,
 Thomas

Attachment: pgp00000.pgp
Description: PGP signature

References:
- Avoid use of libgcc_s and libgcc_eh when building glibc
  - From: Joseph S. Myers
- Re: Avoid use of libgcc_s and libgcc_eh when building glibc
  - From: Roland McGrath
- Re: Avoid use of libgcc_s and libgcc_eh when building glibc
  - From: Joseph S. Myers

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