public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Problem compiling GCC 3.2 on i686-pc-linux: "not enough room for program headers"
Date: Tue, 29 Oct 2002 17:11:00 -0000	[thread overview]
Message-ID: <m3d6psn3b0.fsf@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <006201c27f9d$c23a9f50$fd01a8c0@rhizome.org>

>>>>> "Francis" == Francis Hwang <francis@rhizome.org> writes:

  Francis> I'm trying to compile GCC 3.2, and configure seems to work, but then when I
  Francis> make, I get this error:

  Francis> checking whether the C compiler (...) works... no
  Francis> configure: error: installation or configuration problem: C compiler cannot
  Francis> create executables.

  Francis> /usr/bin/ld: conftest: Not enough room for program headers (allocated 6,
  Francis> need 7)
  Francis> /usr/bin/ld: final link failed: Bad value

What kind of system do you have?  What does `sh config.guess' say?
Is /usr/bin/ld a native linker, or the GNU linker?

Ben


  reply	other threads:[~2002-10-30  1:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 14:51 Francis Hwang
2002-10-29 17:11 ` Ben Elliston [this message]
2002-10-30  9:55   ` Francis Hwang
2002-10-30 17:02     ` Ben Elliston
2002-10-31 11:16       ` Francis Hwang
2002-11-22  9:17     ` CPP (preprocessor) quandry Eljay Love-Jensen
2002-11-22  9:43       ` Buddy Lott
2002-11-22 10:06         ` Eljay Love-Jensen
2002-11-22 10:11           ` Buddy Lott
2002-11-22 10:32             ` Eljay Love-Jensen
2002-11-01 10:00 Problem compiling GCC 3.2 on i686-pc-linux: "not enough room for program headers" Francis Hwang

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=m3d6psn3b0.fsf@scooby.brisbane.redhat.com \
    --to=bje@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).