public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin von Loewis <loewis@informatik.hu-berlin.de>
To: gcc-gnats@gcc.gnu.org
Subject: target/6688: sparcv9/libgcc.so not installed
Date: Fri, 17 May 2002 02:16:00 -0000	[thread overview]
Message-ID: <200205170909.g4H99tLw028058@paros.informatik.hu-berlin.de> (raw)


>Number:         6688
>Category:       target
>Synopsis:       sparcv9/libgcc.so not installed
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 17 02:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Martin v. Loewis
>Release:        3.1
>Organization:
HUB
>Environment:
System: SunOS 5.9 Beta_Refresh sun4u sparc SUNW,Sun-Blade-1000
Architecture: sun4

	
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: ../configure --host=sparc-sun-solaris2.8 --enable-shared --enable-threads --with-cpu=v8 --with-gnu-ld --with-gnu-as --enable-version-specific-runtime-libs
>Description:
	When building binaries with gcc -m64, they won't link against
	libgcc_s.so.1, but libgcc.a. The cause of this problem is that
	no file lib/gcc-lib/sparc-sun-solaris2.8/3.1/sparcv9/libgcc.so
	is created.
>How-To-Repeat:
	Compile
	int main(){}
	with
	gcc -o a -m64 a.so
	then execute
	ldd a
>Fix:
	Create a symlink for libgcc_s.so.1 in sparcv9
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-17  9:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17  2:16 Martin von Loewis [this message]
2002-05-17  2:31 davem

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=200205170909.g4H99tLw028058@paros.informatik.hu-berlin.de \
    --to=loewis@informatik.hu-berlin.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).