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: David Miller <davem at davemloft dot net>
To: joseph at codesourcery dot com
Cc: roland at hack dot frob dot com, libc-alpha at sourceware dot org, ryan dot arnold at gmail dot com, krebbel at linux dot vnet dot ibm dot com, thomas at codesourcery dot com, kkojima at rr dot iij4u dot or dot jp, vapier at gentoo dot org
Date: Wed, 30 May 2012 16:15:59 -0400 (EDT)
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>

From: "Joseph S. Myers" <joseph@codesourcery.com>
Date: Wed, 30 May 2012 10:59:46 +0000 (UTC)

> I'd like architecture maintainers to test this, for all libc architectures 
> and for IA64.

I'll do some sparc testing for you today.

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]