public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: "Munagala V. S. Ramanath" <ram@netcom.com>
Cc: Manfred.Hollstein@ks.sel.alcatel.de, manfred@s-direktnet.de,
	egcs@cygnus.com
Subject: Re: SunOS shared libs ?
Date: Wed, 08 Jul 1998 22:15:00 -0000	[thread overview]
Message-ID: <14465.899961057@hurl.cygnus.com> (raw)
In-Reply-To: <199806101546.IAA05334@netcom13.netcom.com>

  In message < 199806101546.IAA05334@netcom13.netcom.com >you write:
  > write_c_file - output name is ../../../lib/libtype1.so, prefix is libtype1_
  > so
  > static int count;
  > typedef void entry_pt();
  > void _GLOBAL__FI_libtype1_so() {
  >         ++count;
  > }
Here's the reason why you still need the -fPIC option when building
a shared library out of just pure C code.  The reference to "count"
must be PIC.  I don't know why we need to increment that counter.
Someone familiar with C++ and collect2 would have to comment.

jeff

  parent reply	other threads:[~1998-07-08 22:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-08  7:59 Munagala V. S. Ramanath
1998-06-11 11:04 ` Manfred Hollstein
1998-07-08 22:15 ` Jeffrey A Law [this message]
1998-07-09  9:13   ` Manfred Hollstein
1998-07-09 22:16     ` Jeffrey A Law
1998-07-10  7:01       ` Manfred Hollstein
  -- strict thread matches above, loose matches on Subject: below --
1998-07-09  8:45 Munagala V. S. Ramanath
1998-07-09 10:46 ` Jeffrey A Law
1998-06-10  7:36 Munagala V. S. Ramanath
1998-06-10 12:47 ` Manfred.Hollstein
1998-06-10  9:23   ` Jeffrey A Law
1998-06-11 11:04     ` Manfred Hollstein
1998-06-09  7:48 Munagala V. S. Ramanath
1998-06-10  4:39 ` Manfred Hollstein

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=14465.899961057@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=Manfred.Hollstein@ks.sel.alcatel.de \
    --cc=egcs@cygnus.com \
    --cc=manfred@s-direktnet.de \
    --cc=ram@netcom.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).