public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aj@suse.de
To: gcc-gnats@gcc.gnu.org
Subject: objc/2145: objc testsuite fails since libgcc_so.0 is not found
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <20010302075030.D530A1EA2E@gromit.rhein-neckar.de> (raw)
>Number: 2145
>Category: objc
>Synopsis: objc testsuite fails since libgcc_so.0 is not found
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 02 00:16:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Andreas Jaeger
>Release: 3.0 20010301 (prerelease)
>Organization:
>Environment:
System: Linux gromit 2.4.2 #69 Thu Feb 22 20:42:07 CET 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: /cvs/gcc-3_0-branch/configure --prefix=/opt/gcc-3.0-test --enable-shared --enable-threads=posix --with-gnu-as --with-gnu-ld --disable-nls --with-system-zlib --enable-languages=c,objc,c++,f77
>Description:
Running the testsuite in a chroot jail without libgcc_s.so
installed, all objc tests fail. The log files show:
/usr/bin/ld: warning: libgcc_s.so.0, needed by /usr/src/packages/BUILD/gcc/obj/i686-pc-linux-gnu/libobjc/.libs/libobjc.so, not found (try using -rpath or -rpath-link)
/usr/src/packages/BUILD/gcc/obj/i686-pc-linux-gnu/libobjc/.libs/libobjc.so: undefined reference to `__eprintf@GCC_3.0'
collect2: ld returned 1 exit status
compiler exited with status 1
We need to pass rpath correctly to that file. Otherwise the
tests will fail - or the wrong version of libgcc_s.so is used
in case that it gets upgraded.
>How-To-Repeat:
Run the testsuite without installing libgcc_s.so.0.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 0:00 aj [this message]
2003-03-25 1:41 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:
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=20010302075030.D530A1EA2E@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=gcc-gnats@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).