From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: jakub@redhat.com
Cc: binutils@sources.redhat.com
Subject: Re: [PATCH] Reserve a few .dynamic entries
Date: Wed, 06 Jun 2001 10:32:00 -0000 [thread overview]
Message-ID: <200106061732.TAA28233@ignucius.axis.se> (raw)
In-Reply-To: <20010606181338.P1253@sunsite.ms.mff.cuni.cz>
> Date: Wed, 6 Jun 2001 18:13:38 +0200
> From: Jakub Jelinek <jakub@redhat.com>
> +DYNAMIC=".dynamic ${RELOCATING-0} : { *(.dynamic) ${RELOCATING+FILL(0) . += 6 * ${ELFSIZE} / 4; } }"
Oh, and I think you need tp rewrite that to not have a '}' in
the '+'-part. IIRC it breaks with solaris /bin/sh. Ask Alex
Oliva.
brgds, H-P
PS. Looking forward to that prelinking stuff.
next prev parent reply other threads:[~2001-06-06 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 9:10 Jakub Jelinek
2001-06-06 10:15 ` Hans-Peter Nilsson
2001-06-08 11:13 ` [PATCH] Reserve a few .dynamic entries (take 2) Jakub Jelinek
2001-06-08 12:10 ` Hans-Peter Nilsson
2001-06-06 10:32 ` Hans-Peter Nilsson [this message]
2001-06-06 16:45 ` [PATCH] Reserve a few .dynamic entries Ben Elliston
2001-06-08 15:04 ` Ulrich Drepper
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=200106061732.TAA28233@ignucius.axis.se \
--to=hans-peter.nilsson@axis.com \
--cc=binutils@sources.redhat.com \
--cc=jakub@redhat.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).