This is the mail archive of the
mailing list for the glibc project.
Re: Support installing headers for bootstrapping libgcc
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Roland McGrath <roland at hack dot frob dot com>, libc-alpha at sourceware dot org
- Date: Fri, 11 May 2012 11:02:52 -0400
- Subject: Re: Support installing headers for bootstrapping libgcc
- References: <Pine.LNX.firstname.lastname@example.org><20120309190400.552E82C0A7@topped-with-meat.com><Pine.LNX.email@example.com><20120323000616.32F372C08D@topped-with-meat.com><Pine.LNX.firstname.lastname@example.org>
On Fri, May 11, 2012 at 9:53 AM, Joseph S. Myers
> So how should these static linking issues be addressed? ?By arranging for
> the versions of the functions that use dlopen to be used in sln and
> ldconfig? ?By arranging for dummy versions that just abort to be used in
> those programs? ?By having appropriate makefile variables and targets to
> build and install glibc without these programs and then later build and
> install these programs after libgcc_eh has been built and installed?
I like the last option.
The other options can lead to confusion (broken static programs) and
problems (what libraries will dlopen load).