On Sun, Jan 17, 2021 at 1:06 PM Tom Honermann via Gcc <gcc@gcc.gnu.org> wrote: > > Hi all. I've been trying to build a custom gcc (trunk) with a custom > glibc (trunk) with support for C and C++ on x86_64 Linux and have so far > been unsuccessful at identifying a sequence of configure/make > invocations that completes successfully. I'm not trying to build a > cross compiler. > > The scenario I'm trying to satisfy is testing some changes to gcc, and > additional changes to libstdc++ that have new autoconf and header > dependencies on the presence of new functions in existing glibc headers. > > The glibc installation I'm trying to use was built with: > > mkdir glibc-build > cd glibc-build > ../glibc/configure \ > CC=gcc \ > CXX=g++ \ > --prefix /.../glibc > make && make install > > For gcc, I've tried numerous variants of the following: > > mkdir gcc-build > cd gcc-build > ../gcc/configure \ > CC=gcc \ > CXX=g++ \ > --prefix /.../gcc \ > --disable-multilib \ > --enable-languages=c,c++ \ > --enable-checking=release \ > --disable-bootstrap \ > --disable-lto > > Things I've tried include setting CFLAGS, CXXFLAGS, and LDFLAGS to > specify additional glibc paths, to specify alternate paths (via > -nostdinc/-nostdinc++), setting LIBRARY_PATH and CPATH, passing > --with-sysroot, passing --with-headers and --with-libs, passing > --with-native-system-header-dir, some of those in conjunction with > removing --disable-bootstrap, and wrapping gcc in a script that attempts > to substitute certain include paths. > > The problem I'm having is that, in every attempt, the glibc headers and > libraries from under /usr end up getting used instead of the custom > glibc ones at some point leading to build failures. > > Does anyone have a recipe available for doing this?
Try scripts/build-many-glibcs.py in glibc source. -- H.J.
