On 10/10/19 8:24 PM, Ken Moffat wrote:
On Thu, Oct 10, 2019 at 06:18:17PM -0500,blf_supp...@lindows.org wrote:
So I follow the book in section 6.21.1. Installation of GCC
SED=sed \
../configure --prefix=/usr \
--enable-languages=c,c++ \
--disable-multilib \
--disable-bootstrap \
--with-system-zlib
This is what it returns
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC
0.8.0+.
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
ftp://gcc.gnu.org/pub/gcc/infrastructure/. See also
http://gcc.gnu.org/install/prerequisites.html 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.
Whenever a configure script tells you that something is missing, you
need to look at the output in config.log to see what fragment it ran
which led it to report that message.
A successful configure run will have a *lot* of tests which appear
to fail (it adapts the build for different systems), and after the
failure configure will dump its state in the log, which again is
rarely interesting.
So, from a term outside chroot find the correct config.log (the
latest, if more than one - gcci can run configure in several
subdirectories although in this case I think it is in the top level
directory) and open that in 'view' or 'less'. Then search for that
error message ('/' to search) :
/Building GCC requires GMP
(on old versions, you might need to escape the spaces with \)
Now look at the lines above that. Usually, a program fragment will
be created and executed. That then (if it fails) returns a
meaningful message which can point to what is broken.
In this case, I took a look at the top level configure script. The
error is specifically for missing/inadequate gmp and is output at
line 5838. Above it, the tests start at line 5473. It first checks
for 'with' options, then the tests start at about line 5629. It
includes gmp.h and reports yes | buggy.acceptable | no (you should
see those when running configure), then repeats for mpfr.h, and then
repeats for mpc.h.
Then it checks all three together and reports yes or no.
Somewhere in those results will be an error (possibly from compiling
or linking).
ĸen
Thanks for the well written and informative response.
Being new to this, I was not aware of the config.log.
Looking, it seems to be doing checks for those libraries.
Maybe I am wrong, but I think I see what the problem is even though it
does not explicitly say what it is.
At the top it is showing the build environment is using the host system
hostname = hx1
uname -m = x86_64
uname -r = 4.9.0-11-amd64
uname -s = Linux
uname -v = #1 SMP Debian 4.9.189-3+deb9u1 (2019-09-20)
I am guessing this is incorrect, and the chroot should be using it's own
environment?
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
