public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: meissner@cygnus.com
To: egcs@cygnus.com, frichard@bbn.com
Subject: Re:  GNU ld on x86 Solaris
Date: Wed, 05 Nov 1997 19:32:00 -0000	[thread overview]
Message-ID: <199711060315.WAA16504@tweedledumb.cygnus.com> (raw)

| I've been tooling around with GNU ld to see if I can get it to work on
| x86 Solaris.  I thought this wouldn't be a problem since GNU ld seems
| to work fine on Sparc Solaris.  But I'm getting this message:
| 
|     ld.new: foo: Not enough room for program headers (allocated 5, need 6)
|     ld.new: final link failed: Bad value
| 
| Here's a complete dump of ld's verbose output.  Perhaps I shouldn't be
| using this version of BFD?  Any help would be appreciated:

A program header is describes a region of memory to the dynamic linker (IMHO
this is a wart in ELF, that there are two different ways of describing memory,
sections being the other).  In any case, for other ELF x86 systems, BFD
believes their will be five regions for programs that contain references to
shared libraries:

   1)	Program header region that contains the program headers themselves;

   2)	The interpreter region that points to the interpreter to invoke to
	start the program;

   3)	The read-only, execute enabled text section;

   4)	The read/write, execute disabled data section;

   5)	The data passed to the dynamic loader.

If BFD claims it needs 6 tables, then you have an extra section that must be
accounted for (such as r/w data in the middle of r/o data).

             reply	other threads:[~1997-11-05 19:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-05 19:32 meissner [this message]
1997-11-05 23:22 ` Fred Richardson
1997-11-05 23:22 ` Fred Richardson
1997-11-06 15:17   ` Michael Meissner
  -- strict thread matches above, loose matches on Subject: below --
1997-11-05 17:54 Fred Richardson
1997-11-05 20:48 ` Ian Lance Taylor

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=199711060315.WAA16504@tweedledumb.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=frichard@bbn.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).