This is the mail archive of the
mailing list for the glibc project.
Re: How to build/test glibc with new gcc
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>, GNU C Library <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 17 Jul 2015 13:01:58 -0400
- Subject: Re: How to build/test glibc with new gcc
- Authentication-results: sourceware.org; auth=none
- References: <55A9324B dot 2090503 at arm dot com>
On 07/17/2015 12:50 PM, Szabolcs Nagy wrote:
> i'm wondering what's the official way to build glibc with new gcc.
> the documentation about building glibc assumes that the host
> compiler is used when doing a native build, but if gcc is installed
> at some prefix path, then the tests don't use the right libraries:
> they use libgcc_s.so.1 and libstdc++.so.6 of the host (or fail
> when the host does not have these).
> Using LD_LIBRARY_PATH does not work as the tests override the
> library path, but i assume this can be solved by either adding
> -Wl,-rpath=/gcc/prefix/lib to the LDFLAGS of the tests or
> copying the compiler runtime into the build path:
> export PATH="/path/to/gcc-prefix/bin:$PATH"
> cp -a /path/to/gcc-prefix/lib*/*.so* .
> /path/to/glibc-src/configure --prefix=/usr
> make -j
> make check
> is there a cleaner way to do it?
Yes, don't use native builds. You must configure everything as
if you were in a cross-compilation environment, that way you get
sysroot isolation which you need.
The safest thing after that is to convince Joseph Myers that
--enable-poison-system-directories should go upstream? This
provides assurances that you don't touch the system headers.