public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Olaf van der Spek <olafvdspek@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: Support for automatic linking via pragma
Date: Fri, 04 Mar 2011 16:44:00 -0000	[thread overview]
Message-ID: <AANLkTi=CZRDnpi5dJOyamgBHA2ckzQFEb3qyhV7gsLSA@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimCxKpnqFZ34ELdejO6JY-CCvX_fhkSB6SWYSzF@mail.gmail.com>

On Fri, Mar 4, 2011 at 8:29 AM, Olaf van der Spek <olafvdspek@gmail.com> wrote:
> On Mon, Feb 28, 2011 at 7:17 PM, Olaf van der Spek <olafvdspek@gmail.com> wrote:
>> Hi,
>>
>> I've submitted a feature request for automatic linking via pragma:
>> http://sourceware.org/bugzilla/show_bug.cgi?id=12485
>> What do others think about the idea?
>
> Somebody?
>
> Let me quote the request:
> MSVC supports the following pragma, which can be used to automatically link a
> library when a header file is included. This is used by for example Boost.
>
> It makes linking with the right lib a lot simpler. No more fiddling
> with autoconf to detect the right lib name.
>

Not necessarily.  Unlike DSO, object files don't have ABI/API
information. You may not link foo.o compiled with glibc 2.5/libbar
1.3 against glibc 2.13/libbar 1.9

-- 
H.J.

  reply	other threads:[~2011-03-04 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 18:17 Olaf van der Spek
2011-03-04 16:30 ` Olaf van der Spek
2011-03-04 16:44   ` H.J. Lu [this message]
2011-03-04 16:52     ` Ian Lance Taylor
2011-03-04 16:55       ` H.J. Lu
2011-03-04 17:31         ` Kai Tietz
2011-03-04 17:35           ` Olaf van der Spek
2011-03-04 18:40         ` Ian Lance Taylor
2011-03-04 17:31     ` Olaf van der Spek

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='AANLkTi=CZRDnpi5dJOyamgBHA2ckzQFEb3qyhV7gsLSA@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=olafvdspek@gmail.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).