bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug libctf/27482] parallel make -j 16 install falls over in 2.36


From: krentel at rice dot edu
Subject: [Bug libctf/27482] parallel make -j 16 install falls over in 2.36
Date: Thu, 04 Mar 2021 17:05:38 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=27482

--- Comment #3 from Mark Krentel <krentel at rice dot edu> ---
So far, I'm unable to test your branch.  I can't get past the 'make'
stage, either in your branch or master.

As you know, the git repo also contains gdb, but the release tar files
do not.  That's where I'm stuck.  It keeps trying to build gdb and
fails in the sub-configure for gdb over detecting gpm.

I've added config options for gpm, mpc, mpfr (spack built, if you're
familiar with spack) as:

configure  \
    prefix="$prefix"   \
    --disable-dependency-tracking   \
    --disable-werror    \
    --enable-multilib   \
    --enable-shared     \
    --enable-64-bit-bfd    \
    --enable-targets=all   \
    --with-system-zlib   \
    --with-sysroot=/   \
   
--with-gmp=/home/krentel/fix-jobs/install-spack/linux-rhel8-x86_64/gcc-8.3.1/gmp-6.1.2-uzctzx4mfpqvuvttsnr4fc3uhavg376z
 \
   
--with-mpc=/home/krentel/fix-jobs/install-spack/linux-rhel8-x86_64/gcc-8.3.1/mpc-1.1.0-56oiroosmaeefr7cghp5xkswqk7vsesd
 \
   
--with-mpfr=/home/krentel/fix-jobs/install-spack/linux-rhel8-x86_64/gcc-8.3.1/mpfr-4.0.2-v3zmpms3lu6yfoi4p4x26fifa5j4pmda

And it fails in the sub-configure for gdb (this is in step make) as:

checking for library containing dlopen... none required
checking whether to use expat... auto
checking for libexpat... no
configure: WARNING: expat is missing or unusable; some features may be
unavailable.
checking for libgmp... no
configure: error: GMP is missing or unusable
make[1]: *** [Makefile:11412: configure-gdb] Error 1
make[1]: Leaving directory '/home/krentel/fix-jobs/build-master'
make: *** [Makefile:903: all] Error 2

I'd like to tell it not to build gdb at all.
How do I do that?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]