public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: jakub@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/6668: when using --disable-multilib, libgcc_s.so is installed in the wrong place on sparc-solaris
Date: Wed, 14 Aug 2002 09:56:00 -0000	[thread overview]
Message-ID: <20020814160601.27178.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/6668; it has been noted by GNATS.

From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: jakub@gcc.gnu.org
Cc: dann@godzilla.ics.uci.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org, jakub@gcc.gnu.org
Subject: Re: target/6668: when using --disable-multilib, libgcc_s.so is installed in the wrong place on sparc-solaris
Date: 14 Aug 2002 18:02:33 +0200

 jakub@gcc.gnu.org writes:
 
 > Synopsis: when using --disable-multilib, libgcc_s.so is installed in the wrong place on sparc-solaris
 > 
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: jakub
 > State-Changed-When: Thu May 16 06:35:02 2002
 > State-Changed-Why:
 >     I think we'll need driver changes then, the guess method
 >     used in mklibgcc really doesn't work well with --disable-multilibs.
 >     I think it will be useful anyway, for libtool etc.
 >     IMHO there should be an option -print-multi-suffix
 >     similar to -print-multi-directory, which would print
 >     empty line with -print-multi-directory would print .,
 >     /directory if -print-multi-directory would print directory
 >     and in the sparc/s390/x86_64/etc. cases would print
 >     the libdir suffix instead, so
 >     gcc -m64 -print-multi-suffix would print on sparc64-linux
 >     64
 >     and on sparc-solaris
 >     /sparcv9
 >     Will try to implement this soon.
 
 Have you been able to work on this?  I've just received a report that (as
 expected ;-) IRIX 6 with --disable-multilib is affected by this problem as
 well.  As on Solaris 2, you must configure this way on systems that cannot
 run 64-bit binaries for whatever reason, so this certainly should be fixed
 for 3.3 (if not for 3.2.1).
 
 	Rainer


             reply	other threads:[~2002-08-14 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14  9:56 Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-10 12:03 jakub
2002-05-16  6:35 jakub
2002-05-16  4:12 davem
2002-05-15 15:16 Dan Nicolaescu

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=20020814160601.27178.qmail@sources.redhat.com \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jakub@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).