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: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, libc-alpha at sourceware dot org
- Date: Fri, 17 Jul 2015 13:40:11 -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> <55A93549 dot 8090703 at linaro dot org>
On 07/17/2015 01:03 PM, Adhemerval Zanella wrote:
> On 17-07-2015 13:50, 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?
> I used to apply a modified version of , configure and install GCC
> in a different folder than system one. Unfortunately I think Meissner
> patch did not land in upstream.
>  https://gcc.gnu.org/ml/gcc-patches/2012-05/msg02097.html
Don't sysroot'd builds solve this problem?