From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: George R Goffe <grgoffe@yahoo.com>
Cc: Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Is this a bug or UFU?
Date: Fri, 8 Apr 2022 17:57:12 +0100 [thread overview]
Message-ID: <CAH6eHdST2BXwLFVrVL62yOgh4U0=nqNpzgCk+NfPeh+83h=gbw@mail.gmail.com> (raw)
In-Reply-To: <1488577238.235399.1649435475723@mail.yahoo.com>
On Fri, 8 Apr 2022 at 17:32, George R Goffe via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Howdy,
>
> I'm building gcc (and gmp/mpfr/mpc) from the repository and am having trouble. Could you take a peek and let me know what I'm doing wrong please?
>
> Best regards and BE SAFE!
>
> George...
>
>
> fc37-bash 5.1 /tools/gcc# cd obj-x86_64-pc-linux-gnu/
> fc37-bash 5.1 /tools/gcc/obj-x86_64-pc-linux-gnu# ../gcc/configure --prefix=/usr/lsd/$osname --verbose \
> --with-mpc=/usr/lsd/$osname \
> --with-mpfr=/usr/lsd/$osname \
> --with-gmp=/usr/lsd/$osname \
Stop right there. Don't do that.
Read https://gcc.gnu.org/wiki/InstallingGCC instead, and do what it says.
> --disable-werror \
> --disable-multilib
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking target system type... x86_64-pc-linux-gnu
> checking for a BSD-compatible install... /usr/lsd/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 libatomic support... yes
> checking for libitm support... yes
> checking for libsanitizer support... yes
> checking for libvtv support... yes
> checking for libphobos support... yes
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> 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 gcc option to accept ISO C99... none needed
> 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 gnatbind... no
> checking for gnatmake... no
> checking whether compiler driver understands Ada... no
> checking for gdc... gdc
> checking whether the D compiler works... 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... yes
> checking for the correct version of mpc.h... no
> configure: error: Building GCC requires GMP 4.2+, MPFR 3.1.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
> https://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.
>
prev parent reply other threads:[~2022-04-08 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1488577238.235399.1649435475723.ref@mail.yahoo.com>
2022-04-08 16:31 ` George R Goffe
2022-04-08 16:57 ` Jonathan Wakely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdST2BXwLFVrVL62yOgh4U0=nqNpzgCk+NfPeh+83h=gbw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=grgoffe@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).