public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: ronf <ron@dock.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Building GCC Failed: stubs-32.h missing
Date: Mon, 10 Feb 2014 21:38:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.10.1402102236000.7745@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <1392066249429-1010178.post@n5.nabble.com>

On Mon, 10 Feb 2014, ronf wrote:

> I want to build gcc from source on my CentOS 6 x86-64 Linux system, but I am
> having a serious problem with the "configure" scripts and make files. The
> build process insists on accessing "stubs-32.h" even though my Linux system
> lacks this header file. My system has stubs.h and stubs-64.h header files in
> the /usr/include/gnu directory. The content of stubs.h is shown here:

Surely Google is your friend? Gcc-4.9 will print this message:

I suspect your system does not have 32-bit developement libraries (libc 
and headers). If you have them, rerun configure with --enable-multilib. If 
you do not have them, and want to build a 64-bit-only compiler, rerun 
configure with --disable-multilib.


-- 
Marc Glisse

  reply	other threads:[~2014-02-10 21:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 21:04 ronf
2014-02-10 21:38 ` Marc Glisse [this message]
2014-02-11  0:40   ` Kai Ruottu
2014-02-11  0:46 ` Jonathan Wakely
2014-02-12 15:04   ` Soufien Hidouri
2014-02-13 23:34 ` ronf
2014-02-14  9:35   ` Jonathan Wakely
2014-02-14 12:50   ` Andrew Haley
2014-02-20 20:39     ` ronf
2014-02-21  9:42       ` Andrew Haley

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=alpine.DEB.2.10.1402102236000.7745@laptop-mg.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ron@dock.net \
    /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).