From: "Michalski, Rafał" <RMichalski@era.pl>
To: 'Alexandre Oliva' <aoliva@redhat.com>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: RE: cannot link [against] shared libraries
Date: Fri, 27 Jul 2001 08:58:00 -0000 [thread overview]
Message-ID: <E4E3EF945695D411BCDC009027AC88400135FD3A@ra.pc.eragsm.com.pl> (raw)
> > After upgrading my compiler to 3.0,
> > I am no longer able to link against
> > the Xerces XML parser shared library.
>
> You'll have to rebuild that library. GCC 3.0 has adopted the new
> multi-vendor C++ ABI, which required changes in the representation of
> types and modifications in name mangling.
Good!
It works now, thanks lot!
And debugger sees in nested scopes.
I only had to remove -instances=static from Makefile.tmpl
- interesting for Xerces users, however.
Still wondering what with old compiled stuff.
I'm getting to prick openldap libs for first.
Yours
Rafal
next reply other threads:[~2001-07-27 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 8:58 Michalski, Rafał [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-27 8:58 Michalski, Rafał
2001-07-27 10:04 ` Rob Newberry
2001-07-27 1:38 Michalski, Rafał
2001-07-27 1:57 ` Alexandre Oliva
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=E4E3EF945695D411BCDC009027AC88400135FD3A@ra.pc.eragsm.com.pl \
--to=rmichalski@era.pl \
--cc=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
/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).