public inbox for
help / color / mirror / Atom feed
Subject: other/9691: Shared libraries don't work with g++
Date: Thu, 13 Feb 2003 12:16:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         9691
>Category:       other
>Synopsis:       Shared libraries don't work with g++
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 13 12:16:00 UTC 2003
>Originator:     Christian Corti
>Release:        gcc 3.2.1
DECstation 5000/260 MIPS R4400; NetBSD 1.6;
g++ can't create working or use shared libraries.
Programs linked against such libraries will crash on loading with a segmentation
My test program compiled with 'g++-3.2 -o test':
#include <iostream>
  std::cout << "Hello!\n";

Output of 'ldd test'
        -lm.0 => /usr/lib/
        -lstdc++.5 => /usr/local/lib/
        -lc.12 => /usr/lib/
        -lgcc_s.1 => /usr/local/lib/

Output of 'gcc-3.2 -v'
Configured with: ../gcc-3.2.1/configure --host=mipsel-dec-netbsd1.6
--program-suffix=-3.2 --with-ld=/usr/local/bin/ld

Output of '/usr/local/bin/ld -v':
GNU ld version

Output of '/usr/local/bin/as -v':
GNU assembler version (mipsel-dec-netbsd1.6) using
BFD version

Output of 'gdb test test.core'
#0  0x5ffe5b30 in _rtld_relocate_objects () from /usr/libexec/ld.elf_so

Creating a statically linked version of this program works,
i.e. "g++-3.2 -static -o test" produces a working
'test' program.

The same problem occurs with binutils 2.11.2.
binutils 2.9.1 can't be used for compiling gcc 3.2.1 on
mipsel as this will lead to an assembler error during
compilation of one of the libgcc files.

I tried g++ 3.2.1 on a SUN 4/260 (sun4) with SunOS 4.1.1
and it is broken too. gcc 3.2.1 however works fine on all
Any program compiled with g++ will crash on loading.


             reply	other threads:[~2003-02-13 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 12:16 Christian.Corti [this message]
2003-05-14 19:46 Dara Hazeghi
2003-05-15  4:38 bangerth

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).