public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: Nick Clifton <nickc@redhat.com>
Cc: jbaker@qnx.com, binutils@sources.redhat.com
Subject: Re: [PATCH] Add --warn-shared-textrel option to ld
Date: Thu, 24 Mar 2005 03:50:00 -0000	[thread overview]
Message-ID: <1111603325.15967.192.camel@localhost> (raw)
In-Reply-To: <416557CA.3080803@redhat.com>

Is the check for info->shared suitable for info->pie as well?

Would there be anyway to perhaps make this check a little more verbose
in it's diagnostic output in order to help aid in tracking down the
offending relocations in object files. Suns link editor seems to behave
this way when given a -z text option.
http://docs.sun.com/app/docs/doc/816-1386/6m7qcobl6?a=view (Under PIC)


On Thu, 2004-10-07 at 15:50 +0100, Nick Clifton wrote:
> Hi Jeff,
> 
> >>    * The formatting of the code added to elflink.c does not follow the 
> >> GNU Coding Standards; (the opening curly brace should be on its own
> >> line).
> >>
> >>    * The patch adds a new command line switch to the linker, but it does
> >> not add documentation on this switch to the ld.texinfo file, nor does it
> >> add a line to the ld/NEWS file.
> 
> > How about now?
> 
> Better - thanks:
> 
> > 2004-10-01  Jeff Baker  <jbaker@qnx.com>
> > 	* elflink.c (_bfd_elf_add_dynamic_entry): Add code to
> > 	warn if adding a DT_TEXTREL to a shared object and
> > 	--warn-shared-textrel was specified.
> > 
> > 2004-10-01  Jeff Baker  <jbaker@qnx.com>
> > 	* bfdlink.h (bfd_link_info): Add boolean
> > 	warn_shared_textrel.
> > 
> > 2004-10-01  Jeff Baker  <jbaker@qnx.com>
> > 	* NEWS: Added mention of --warn-shared-textrel option.
> > 	* ld.texinfo: Add documentation for --warn-shared-textrel.
> > 	* lexsup.c: Handle --warn-shared-textrel option.
> 
> Approved and applied.
> 
> Cheers
>    Nick
> 
-- 
Ned Ludd <solar@gentoo.org>

      reply	other threads:[~2005-03-23 18:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 18:31 Jeff Baker
2004-09-21 18:16 ` Jeff Baker
2004-09-30 17:30 ` Nick Clifton
2004-10-01 14:42   ` Jeff Baker
2004-10-07 14:46     ` Nick Clifton
2005-03-24  3:50       ` Ned Ludd [this message]

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=1111603325.15967.192.camel@localhost \
    --to=solar@gentoo.org \
    --cc=binutils@sources.redhat.com \
    --cc=jbaker@qnx.com \
    --cc=nickc@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).