public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred.Hollstein@ks.sel.alcatel.de
To: ram@netcom.com, law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: SunOS shared libs ?
Date: Wed, 10 Jun 1998 12:47:00 -0000	[thread overview]
Message-ID: <13694.39488.317757.302619@slsvhmt> (raw)
In-Reply-To: <199806101435.HAA20756@netcom13.netcom.com>

On Wed, 10 June 1998, 07:35:59, ram@netcom.com wrote:

 > > You need to add "-fPIC" to the linker command line  as well. If any of
 > > your  *.o files  contain  static CTOR/DTORs, a   small .c file will be
 > > generated by the  collect2 program which  in turn will be compiled and
 > > linked into  your shared lib.  Since you  didn't specify "-fPIC"  when
 > > linking, bloody  StunOS ld starts complaining...  Of course, using GNU
 > > ld (e.g. from  binutils-2.9.1) would cure  this; the current  mainline
 > > sources (the  snapshots)  address  this   differently, i.e.  you   can
 > > continue using SunOS ld.
 > 
 >     Ok, thanks that seems to have fixed the problem. I'd strongly
 >     suggest adding this to the FAQ.

Jeff Law, do you think it's worthwhile?

 > 
 >     I still don't understand a couple of items:
 >     -- My files are all C (no C++) so there is CTOR/DTOR issue at all;
 >        how come I still need the -fPIC linker option ?
 >     -- How come I did not need -fPIC linker option with gcc-2.7.2 ?

Looks like your pulling in some C++ related stuff, e.g. via libgcc.a?

Try adding `-Wl,-debug' to your linker command; it'll tell you lots of
information about which CTOR/DTORs have been found and the like.

 > 
 >     Anyway, thanks for the help.
 > 
 >     Ram

manfred

  reply	other threads:[~1998-06-10 12:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-10  7:36 Munagala V. S. Ramanath
1998-06-10 12:47 ` Manfred.Hollstein [this message]
1998-06-10  9:23   ` Jeffrey A Law
1998-06-11 11:04     ` 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-07-08  7:59 Munagala V. S. Ramanath
1998-06-11 11:04 ` Manfred Hollstein
1998-07-08 22:15 ` Jeffrey A Law
1998-07-09  9:13   ` Manfred Hollstein
1998-07-09 22:16     ` Jeffrey A Law
1998-07-10  7:01       ` 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=13694.39488.317757.302619@slsvhmt \
    --to=manfred.hollstein@ks.sel.alcatel.de \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --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).