Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: klibc@zytor.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [klibc] [parisc-linux] klibc parisc64
Date: Mon, 24 Jul 2006 15:41:50 -0700	[thread overview]
Message-ID: <44C54CAE.5050302@zytor.com> (raw)
In-Reply-To: <200607241935.k6OJZkNs000939@hiauly1.hia.nrc.ca>

John David Anglin wrote:
>>> hppa64-linux-gnu-ld: usr/klibc/libc.so: Not enough room for program headers (allocated 5, need 6)
> 
> Additional phdrs are provided by elf64_hppa_additional_program_headers
> in bfd/elf64-hppa.c.  The code doesn't expect a .interp section in
> a shared library.  That would appear to be the problem here.
> 

(k)libc.so isn't a shared library in the ELF sense.  It's an executable.

klibc doesn't do dynamic linking at all.  As Dave said, dynamically 
linked doesn't imply the presence of shared libraries; the converse is 
also true.

	-hpa

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2006-07-24 22:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-24 18:27 [parisc-linux] klibc parisc64 Kyle McMartin
2006-07-24 19:01 ` John David Anglin
2006-07-24 19:28   ` Kyle McMartin
2006-07-24 19:50     ` John David Anglin
2006-07-24 19:35   ` John David Anglin
2006-07-24 22:41     ` H. Peter Anvin [this message]
2006-07-24 22:55       ` [klibc] " H. Peter Anvin
2006-07-24 23:11         ` John David Anglin
2006-07-24 23:17           ` H. Peter Anvin
2006-07-25  1:46             ` Kyle McMartin
2006-07-25  3:09               ` John David Anglin

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=44C54CAE.5050302@zytor.com \
    --to=hpa@zytor.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=klibc@zytor.com \
    --cc=parisc-linux@lists.parisc-linux.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