public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "billingd at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14948] New: irix6.5 bootstrap fails in mabi=64/libobj
Date: Wed, 14 Apr 2004 00:01:00 -0000	[thread overview]
Message-ID: <20040413234932.14948.billingd@gcc.gnu.org> (raw)

irix6.5 bootstrap fails in mabi-64/libobj while linking libobjc.so

Last successful build was cvs updated Wed Apr 7 09:32:15 GMT 2004
First failure was approx 24 hours later.

Failure is:

./libtool --mode=link  /disk4/billingd/obj/gcc/gcc/xgcc -
B/disk4/billingd/obj/gcc/gcc/ -B/disk4/billingd/tmp/gcc/mips-sgi-irix6.5/bin/ -
B/disk4/billingd/tmp/gcc/mips-sgi-irix6.5/lib/ -
isystem /disk4/billingd/tmp/gcc/mips-sgi-irix6.5/include -
isystem /disk4/billingd/tmp/gcc/mips-sgi-irix6.5/sys-include -o libobjc.la 
archive.lo class.lo encoding.lo gc.lo hash.lo init.lo linking.lo misc.lo 
nil_method.lo NXConstStr.lo Object.lo objects.lo Protocol.lo sarray.lo 
selector.lo sendmsg.lo thr.lo thr-objc.lo \
        -rpath /disk4/billingd/tmp/gcc/lib \
        -version-info 1:0:0
/disk4/billingd/obj/gcc/gcc/xgcc -B/disk4/billingd/obj/gcc/gcc/ -
B/disk4/billingd/tmp/gcc/mips-sgi-irix6.5/bin/ -B/disk4/billingd/tmp/gcc/mips-
sgi-irix6.5/lib/ -isystem /disk4/billingd/tmp/gcc/mips-sgi-irix6.5/include -
isystem /disk4/billingd/tmp/gcc/mips-sgi-irix6.5/sys-include -
shared  .libs/archive.o .libs/class.o .libs/encoding.o .libs/gc.o .libs/hash.o 
.libs/init.o .libs/linking.o .libs/misc.o .libs/nil_method.o .libs/NXConstStr.o
 .libs/Object.o .libs/objects.o .libs/Protocol.o .libs/sarray.o .libs/selector.
o .libs/sendmsg.o .libs/thr.o .libs/thr-objc.o  -lc  -Wl,-soname -
Wl,libobjc.so.2 `test -n "sgi2.0" && echo -Wl,-set_version -Wl,sgi2.0` -Wl,-
update_registry -Wl,.libs/so_locations -o .libs/libobjc.so.2.0
ld32: FATAL   12 : Expecting n32 objects: .libs/archive.o is n64.
collect2: ld returned 4 exit status
make[4]: *** [libobjc.la] Error 1


Probable cause is missing -mabi=64 flag.  Will investigate.

-- 
           Summary: irix6.5 bootstrap fails in mabi=64/libobj
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: billingd at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: mips-sgi-irix6.5
  GCC host triplet: mips-sgi-irix6.5
GCC target triplet: mips-sgi-irix6.5


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


             reply	other threads:[~2004-04-13 23:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14  0:01 billingd at gcc dot gnu dot org [this message]
2004-04-14  0:17 ` [Bug libobjc/14948] irix6.5 bootstrap fails in mabi=64/libobjc pinskia at gcc dot gnu dot org
2004-04-14  1:06 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-04-15  2:13 ` billingd at gcc dot gnu dot org
2004-04-15  3:41 ` [Bug libobjc/14948] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-04-15 17:39 ` neroden at gcc dot gnu dot org
2004-04-15 17:39 ` cvs-commit at gcc dot gnu dot org
2004-04-16  0:32 ` david dot billinghurst at comalco dot riotinto dot com dot au
2004-04-16 13:44 ` cvs-commit 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=20040413234932.14948.billingd@gcc.gnu.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).