public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
	  Binutils <binutils@sourceware.org>
Subject: Re: RFA: Adding feature for putting system libraries for pe-coff  targets as last in link order
Date: Mon, 14 Sep 2009 08:39:00 -0000	[thread overview]
Message-ID: <4AAE0476.6000409@gmail.com> (raw)
In-Reply-To: <90baa01f0909140039y44143ff6md7ddddf8a1e968b8@mail.gmail.com>

Kai Tietz wrote:
> Hello,
> 
> it is a pretty common issue, that symbols in system libraries are
> possibly replacing own runtime functions, when users are specifying
> additional system libraries by -l option to ld. AFAIK there is at the
> moment no way to say, that a specific library should be imported at
> tail of chain, and not at possition specified.

  Can you give us an example to demonstrate why the solution to the problem
isn't just to tell people "write the libraries in the order you want, rather
than in the wrong order that you don't want, on the command line"?

> Therefore I would like to ask, if there is interest in an extension to
> linker for this. I would suggest for this an linker option -sys-l, or
> -tail-l.

  I'm not sure whether this should really be considered a problem with the
linker, rather than a problem with the GCC driver or wherever the flags are
coming from.  I can't think of a situation where I've ever needed this sort of
option and wished it existed, so I'll reserve judgment until I see what kind
of example usage you're envisaging.

    cheers,
      DaveK

  reply	other threads:[~2009-09-14  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14  7:39 Kai Tietz
2009-09-14  8:39 ` Dave Korn [this message]
2009-09-14  8:56   ` Kai Tietz
2009-09-15  4:38     ` 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=4AAE0476.6000409@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=binutils@sourceware.org \
    --cc=ktietz70@googlemail.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).