This is the mail archive of the 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: Add script to build many glibc configurations

On 11/17/2016 11:52 AM, Zack Weinberg wrote:
> On 11/09/2016 11:27 AM, Joseph Myers wrote:
>> This patch adds a Python (3.5 or later) script to build many different
>> configurations of glibc, including building the required cross
>> compilers first.  It's not intended to change any patch testing
>> requirements, although some people may wish to use it for high-risk
>> patches such as adding warning options ...
> Since this does its own glibc checkout, it's not clear to me how one
> should use it to test a patch(set).  I presume that whatever one does,
> it only affects the "glibcs" step, but what actually do you do?  Do you
> manually update /some/where/src/glibc to contain the code you want
> tested and then run "glibcs", or do you somehow tell
> the name of a branch you want tested, or what?

I went ahead with the setup steps, and they failed during the compilers
phase.  It seems that it's not picking up the host libraries I just
built.  Now what?

$ ./glibc/scripts/ $PWD/glibc-many host-libraries
PASS: host-libraries gmp rm
PASS: host-libraries gmp mkdir
PASS: host-libraries gmp configure
PASS: host-libraries gmp build
PASS: host-libraries gmp check
PASS: host-libraries gmp install
PASS: host-libraries gmp cleanup
PASS: host-libraries mpfr rm
PASS: host-libraries mpfr mkdir
PASS: host-libraries mpfr configure
PASS: host-libraries mpfr build
PASS: host-libraries mpfr check
PASS: host-libraries mpfr install
PASS: host-libraries mpfr cleanup
PASS: host-libraries mpc rm
PASS: host-libraries mpc mkdir
PASS: host-libraries mpc configure
PASS: host-libraries mpc build
PASS: host-libraries mpc check
PASS: host-libraries mpc install
PASS: host-libraries mpc cleanup
PASS: host-libraries done

$ ./glibc/scripts/ $PWD/glibc-many compilers
PASS: compilers-aarch64_be-linux-gnu check-host-libraries
PASS: compilers-aarch64-linux-gnu check-host-libraries
PASS: compilers-alpha-linux-gnu check-host-libraries
PASS: compilers-arm-linux-gnueabi check-host-libraries
PASS: compilers-arm-linux-gnueabihf check-host-libraries
PASS: compilers-armeb-linux-gnueabi check-host-libraries
PASS: compilers-armeb-linux-gnueabi-be8 check-host-libraries
PASS: compilers-armeb-linux-gnueabihf check-host-libraries
PASS: compilers-arm-linux-gnueabi linux mkdir
FAIL: compilers-alpha-linux-gnu gcc-first configure

$ cat
Thu Nov 17 11:50:29 EST 2016

Description: compilers-alpha-linux-gnu gcc-first configure
Command: /home/zack/projects/glibc-many/src/gcc/configure
-linux-gnu --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=alpha-glibc-linux-gnu --with-sysroot=/home/zac
--disable-libsanitizer --disable-libssp --enable-languages=c
--disable-shared --disable-threads --disable-libatomic
--disable-decimal-float --disable-libffi --disable-libgomp
--disable-libitm --disable-libmpx --disable-libquadmath
--without-headers --with-newlib --with-glibc-version=2.24
Path addition:

checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... alpha-glibc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for libcilkrts support... no
checking for libvtv support... no
checking for x86_64-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for x86_64-pc-linux-gnu-g++... no
checking for x86_64-pc-linux-gnu-c++... no
checking for x86_64-pc-linux-gnu-gpp... no
checking for x86_64-pc-linux-gnu-aCC... no
checking for x86_64-pc-linux-gnu-CC... no
checking for x86_64-pc-linux-gnu-cxx... no
checking for x86_64-pc-linux-gnu-cc++... no
checking for x86_64-pc-linux-gnu-cl.exe... no
checking for x86_64-pc-linux-gnu-FCC... no
checking for x86_64-pc-linux-gnu-KCC... no
checking for x86_64-pc-linux-gnu-RCC... no
checking for x86_64-pc-linux-gnu-xlC_r... no
checking for x86_64-pc-linux-gnu-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether g++ accepts -static-libstdc++ -static-libgcc... yes
checking for x86_64-pc-linux-gnu-gnatbind... no
checking for gnatbind... no
checking for x86_64-pc-linux-gnu-gnatmake... no
checking for gnatmake... no
checking whether compiler driver understands Ada... no
checking how to compare bootstrapped objects... cmp --ignore-initial=16
$$f1 $$f2
checking for objdir... .libs
checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC
Try the --with-gmp, --with-mpfr and/or --with-mpc options to specify
their locations.  Source code for these libraries can be found at
their respective hosting sites as well as at  See also for additional info.  If
you obtained GMP, MPFR and/or MPC from a vendor distribution package,
make sure that you have installed both the libraries and the header
files.  They may be located in separate packages.

FAIL: compilers-alpha-linux-gnu gcc-first configure

Thu Nov 17 11:50:30 EST 2016

(I see a libgmp.a (for instance) in install/host-libraries/lib/, but not
in install/compilers/alpha-linux-gnu/sysroot/, which is the only place
the above configure operation might have thought to look for it.)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]