public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bfriesen at simple dot dallas dot tx dot us" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16507] gcc_s not found when linking 64-bit C++
Date: Thu, 15 Jul 2004 04:17:00 -0000 [thread overview]
Message-ID: <20040715041740.3359.qmail@sourceware.org> (raw)
In-Reply-To: <20040713003639.16507.bfriesen@simple.dallas.tx.us>
------- Additional Comments From bfriesen at simple dot dallas dot tx dot us 2004-07-15 04:17 -------
Subject: Re: gcc_s not found when linking 64-bit C++
On Wed, 14 Jul 2004, Bob Friesenhahn wrote:
>
> I will now try using
>
> --disable-multilib --enable-version-specific-runtime-libs
>
> since my objective is to create a directory tree for 100% 64-bit development
> and I don't want to take the risk of failure while upgrading the compiler.
I would like to be able to say that this finally worked as expected,
but it did not. As before, gcc_s is not found because libgcc_s.so is
hidden away in a sparcv9 subdirectory and gcc is not telling the
system linker where to look.
This fails:
% c++64-3.4.1 -o exceptions exceptions.cpp
ld: fatal: library -lgcc_s: not found
ld: fatal: library -lgcc_s: not found
ld: fatal: File processing errors. No output written to exceptions
collect2: ld returned 1 exit status
This succeeds:
% c++64-3.4.1 -L /usr/local/sparc64/lib/gcc/sparc64-sun-solaris2.9/3.4.1/sparcv9 -o exceptions exceptions.cpp
%
Thus far I have not found a permutation of options which installs the
libraries in the right place, or passes the right options to the
system linker so that it can find them.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16507
next prev parent reply other threads:[~2004-07-15 4:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 0:36 [Bug c++/16507] New: " bfriesen at simple dot dallas dot tx dot us
2004-07-13 0:40 ` [Bug c++/16507] " pinskia at gcc dot gnu dot org
2004-07-13 0:42 ` bfriesen at simple dot dallas dot tx dot us
2004-07-13 0:49 ` pinskia at gcc dot gnu dot org
2004-07-13 0:58 ` bfriesen at simple dot dallas dot tx dot us
2004-07-13 6:53 ` ebotcazou at gcc dot gnu dot org
2004-07-13 13:22 ` bfriesen at simple dot dallas dot tx dot us
2004-07-13 13:51 ` ebotcazou at gcc dot gnu dot org
2004-07-13 14:15 ` bfriesen at simple dot dallas dot tx dot us
2004-07-13 14:38 ` ebotcazou at gcc dot gnu dot org
2004-07-15 2:18 ` bfriesen at simple dot dallas dot tx dot us
2004-07-15 4:17 ` bfriesen at simple dot dallas dot tx dot us [this message]
2004-07-15 5:21 ` ebotcazou at gcc dot gnu dot org
2004-07-15 5:23 ` ebotcazou at gcc dot gnu dot org
2004-07-15 13:47 ` bfriesen at simple dot dallas dot tx dot us
2004-07-18 10:04 ` [Bug other/16507] " ebotcazou at gcc dot gnu dot org
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=20040715041740.3359.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).