public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: pooh@msu.ru
Cc: David Edelsohn <dje@watson.ibm.com>, egcs@cygnus.com
Subject: Re: AIX & shared libstdc++
Date: Tue, 07 Oct 1997 23:14:00 -0000	[thread overview]
Message-ID: <9710072130.AA27862@rios1.watson.ibm.com> (raw)
In-Reply-To: <343A933D.207E8FD4@msu.ru>

>>>>> Andrey Slepuhin writes:

Andrey> 1) I obtain many warnings about undefined symbols which are really class names
Andrey> themselves (for example, range_error), so I remove these symbols from export
Andrey> file.

	This may depend on the type of symbol.  I do not know how class
names appear as symbols and how this would appear in an exports list.  A
class name is not an actual method or member.

Andrey> 2) When linking programs with shared libstdc++, I obtain warnings about
Andrey> multiple defined symbols like __eh<something>. After removing these symbols
Andrey> all my test programs linked and worked fine.

	As mentioned in the README.RS6000 file, AIX 4.1 linker became much
more pedantic about warning of duplicate symbols.  These always have been
there and should not affect correctness of the resulting executable.

Andrey> 3) I am worried about shared libstdc++ size (2.3M instead of 3M static). This
Andrey> can be caused differences in library structure (for example a large number of
Andrey> separate modules in ar file), but I cannot check this.

	*Shrug*

David

  reply	other threads:[~1997-10-07 23:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-07  2:18 Andrey Slepuhin
1997-10-07 11:41 ` David Edelsohn
1997-10-07 23:14   ` Andrey Slepuhin
1997-10-07 23:14     ` David Edelsohn [this message]
     [not found] <3439FE5B.53F1D3CC.cygnus.egcs@msu.ru>
1997-10-07  3:15 ` Jason Merrill
1997-10-07  3:48   ` Andrey Slepuhin
1997-10-09  9:26   ` Andrey Slepuhin
1997-10-09 15:14     ` Ian Lance Taylor
1997-10-13  5:05       ` Andrey Slepuhin

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=9710072130.AA27862@rios1.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=egcs@cygnus.com \
    --cc=pooh@msu.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).