public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Groove, Christian" <groove@norcom.de>
To: egcs-bugs@egcs.cygnus.com
Cc: egcs@egcs.cygnus.com
Subject: egcs and shared LIBS on AIX4.1.5
Date: Wed, 31 Mar 1999 23:46:00 -0000	[thread overview]
Message-ID: <81A51A42F329D211904E00A0C9D8E2A0272340@falke.norcom.de> (raw)
Message-ID: <19990331234600.mSFyMtpHfXhm2WpyskQuC45IKrwDeR-m3ftTrhEfRc8@z> (raw)

Hello

i have got a serious problem with the egcs compiler, that also
affects the g++ compiler on the AIX4.1.5 (others too) operating
system.
 
I would like to create shared libraries on that plattfrom written
of course in C++. I would also like to use global (instantiated)
objects/classes, that should be automatically instantiated, when 
the shared lib gets loaded.
This task is a general problem for AIX (with their braindead XCOFF)
linker, true ELF linkers (Linux Solaris) do not have any problems 
with this, provided that you have a good C++ compiler installed 
(i.e. egcs)

OK, IBM also offers an C++ compiler, and in order to get a workaround
they introduced so called priorities pragmas and a ld-linker wrapper,
that helps to create shared libs. 
Due to the poor debugging support and the limited language capabilities
of the IBM compiler, i would like to switch to egcs/g++ and gdb/ddd.

Now the question, who do i introduce priorities in g++, so that the
linker remarks the C++ classes as to be initialized, when the shared
lib gets loaded. 

Thanks in advance

Christian Groove



Christian Groove
NorCom GmbH
81929 Muenchen, Stefan-George-Ring 6
Tel.: + 49 89 93948 271  Fax: + 49 89 93948 111
Mail: groove@norcom.de



             reply	other threads:[~1999-03-31 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-17  2:49 Groove, Christian [this message]
     [not found] ` < 81A51A42F329D211904E00A0C9D8E2A0272340@falke.norcom.de >
1999-03-17 18:49   ` David Edelsohn
1999-03-31 23:46     ` David Edelsohn
1999-03-31 23:46 ` Groove, Christian

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=81A51A42F329D211904E00A0C9D8E2A0272340@falke.norcom.de \
    --to=groove@norcom.de \
    --cc=egcs-bugs@egcs.cygnus.com \
    --cc=egcs@egcs.cygnus.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).