public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rm at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50993] New: IRIX: fails to build in lto for sgi1.0 linker flag
Date: Fri, 04 Nov 2011 14:42:00 -0000	[thread overview]
Message-ID: <bug-50993-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50993

             Bug #: 50993
           Summary: IRIX: fails to build in lto for sgi1.0 linker flag
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rm@gnu.org


While natively building on IRIX 6.5, I get:

/bin/ksh ./libtool --tag=CC --tag=disable-static  --mode=link
/usr/people/multix/gcc-builds/multibuild/./prev-gcc/xgcc
-B/usr/people/multix/gcc-builds/multibuild/./prev-gcc/
-B/usr/multiware/mips-sgi-irix6.5/bin/ -B/usr/multiware/mips-sgi-irix6.5/bin/
-B/usr/multiware/mips-sgi-irix6.5/lib/ -isystem
/usr/multiware/mips-sgi-irix6.5/include -isystem
/usr/multiware/mips-sgi-irix6.5/sys-include    -Wall -Werror -g -O2  -module
-bindir /usr/multiware/libexec/gcc/mips-sgi-irix6.5/4.6.2
-Wc,../libiberty/libiberty.a -static-libstdc++ -static-libgcc  -o
liblto_plugin.la -rpath /usr/multiware/libexec/gcc/mips-sgi-irix6.5/4.6.2
lto-plugin.lo
libtool: link:  /usr/people/multix/gcc-builds/multibuild/./prev-gcc/xgcc
-B/usr/people/multix/gcc-builds/multibuild/./prev-gcc/
-B/usr/multiware/mips-sgi-irix6.5/bin/ -B/usr/multiware/mips-sgi-irix6.5/bin/
-B/usr/multiware/mips-sgi-irix6.5/lib/ -isystem
/usr/multiware/mips-sgi-irix6.5/include -isystem
/usr/multiware/mips-sgi-irix6.5/sys-include    -shared  .libs/lto-plugin.o   
../libiberty/libiberty.a   -Wl,-soname -Wl,liblto_plugin.so.1 `test -n "sgi1.0"
&& func_echo_all "-Wl,-set_version -Wl,sgi1.0"` -Wl,-update_registry
-Wl,.libs/so_locations -o .libs/liblto_plugin.so.1.0
/usr/multiware/bin/ld: sgi1.0: No such file: No such file or directory
collect2: ld returned 1 exit status
gmake[4]: *** [liblto_plugin.la] Error 1
gmake[4]: Leaving directory
`/usr/people/multix/gcc-builds/multibuild/lto-plugin'

configure flags used:
../gcc-4.6.2/configure --prefix=/usr/multiware
--with-local-prefix=/usr/multiware --enable-threads --disable-c-mbchar 
--disable-nls --disable-wchar_t --enable-languages=c,c++,objc
--with-gmp=/usr/multiware --with-mpfr=/usr/multiware
--enable-version-specific-runtime-libs --with-as=/usr/multiware/bin/as
--with-ld=/usr/multiware/bin/ld --with-gnu-ld

ld is gnu ld, 2.18. I tried without gnu ld/as but I  got other strange errors
much earlier. Gcc 4.6.1 has the same error.


             reply	other threads:[~2011-11-04 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 14:42 rm at gnu dot org [this message]
2011-11-28 17:54 ` [Bug bootstrap/50993] " ro at gcc dot gnu.org
2012-05-22  7:24 ` pinskia at gcc dot gnu.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=bug-50993-4@http.gcc.gnu.org/bugzilla/ \
    --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).