public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hjl@lucon.org (H.J. Lu)
To: ian@cygnus.com (Ian Lance Taylor)
Cc: svivanov@pdmi.ras.ru, egcs@cygnus.com
Subject: Re: Why link C with crtstuff? [patch]
Date: Tue, 28 Apr 1998 10:47:00 -0000	[thread overview]
Message-ID: <m0yUETO-000597C@ocean.lucon.org> (raw)
In-Reply-To: <199804281718.NAA02506@subrogation.cygnus.com>

> 
>    From: hjl@lucon.org (H.J. Lu)
>    Date: Tue, 28 Apr 1998 10:13:19 -0700 (PDT)
> 
>    2. Modify the gnu linker to take
> 
> 	   ld ... --local foo,bar,....
> 
>    which will make foo, bar .. local to libfoo.so. I believe everything
>    is almost in binutils 2.9. We just need to add the --local option to
>    ld.
> 
> I don't know if this is the right approach to take.  I'll just note
> that you can already use a version script to force certain symbols to
> be local to a shared library.
> 

That is why I said thet everything was almost in binutils 2.9. But
I'd like to see that force certain symbols to be local to a shared
library is independent of ELF symbol versioning. We should be able
to use it with and without ELF symbol versioning. 

-- 
H.J. Lu (hjl@gnu.org)

  reply	other threads:[~1998-04-28 10:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m0yU6e1-000B93C@svivano.pdmi.ras.ru>
1998-04-28 14:10 ` H.J. Lu
1998-04-28 10:26   ` Ian Lance Taylor
1998-04-28 10:47     ` H.J. Lu [this message]
     [not found] <m0yTYbl-000598C@ocean.lucon.org>
1998-04-26 17:15 ` Sergei Ivanov
1998-04-26 21:56   ` H.J. Lu
1998-04-27 13:59     ` Sergei Ivanov
1998-04-25 17:40 Sergei Ivanov
1998-04-26  0:01 ` Jeffrey A Law
1998-04-26  0:19 ` H.J. Lu
1998-04-26 10:05   ` Jeffrey A Law
1998-04-26 10:26     ` H.J. Lu
1998-04-26 12:08     ` Ian Lance Taylor
1998-04-26 12:45   ` Sergei Ivanov

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=m0yUETO-000597C@ocean.lucon.org \
    --to=hjl@lucon.org \
    --cc=egcs@cygnus.com \
    --cc=ian@cygnus.com \
    --cc=svivanov@pdmi.ras.ru \
    /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).