public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com.au To: java-gnats@sourceware.cygnus.com Subject: libgcj/1240: Cannot build on mips-sgi-irix6.5 - link error Date: Wed, 20 Dec 2000 12:22:00 -0000 [thread overview] Message-ID: <19990809015840.11284.qmail@egcs.cygnus.com> (raw) >Number: 1240 >Category: libgcj >Synopsis: Cannot build on mips-sgi-irix6.5 - link error >Confidential: no >Severity: serious >Priority: medium >Responsible: java-hacker >State: closed >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Dec 20 12:18:10 PST 2000 >Closed-Date: Thu Sep 02 19:38:17 PDT 1999 >Last-Modified: Thu Sep 02 19:38:17 PDT 1999 >Originator: David Billinghurst >Release: gcj-2.95 >Organization: >Environment: mips-sgi-irix6.5 gcc-2.95 >Description: Build fails when linking -mabi=64 version of zlib. Looks like a libtool problem. libtool is passed -mabi=64 on the command line (twice) but the flag isn't passed to gcc, which defaults to -n32 mode >How-To-Repeat: On mips-sgi-irix6.5 host ../../src/gcj-2.95/configure make >Fix: >Release-Note: >Audit-Trail: Formerly PR libgcj/21 From: Tom Tromey <tromey@cygnus.com> To: David.Billinghurst@riotinto.com.au Cc: java-gnats@sourceware.cygnus.com Subject: Re: gcj/21: Cannot build on mips-sgi-irix6.5 - link error Date: Sun, 8 Aug 1999 19:29:48 -0700 Hi. libgcj 2.95 uses libtool 1.2f -- quite an old version. In the cvs repository we are now using 1.3.3, and we plan to use that for the upcoming 2.95.1 release of libgcj. Is there any way you could check out libgcj from the cvs repo and try it? Or, failing that, could you try 1.3.3 with your libgcj? Before I forward this to the libtool maintainers I'd like to see if it is fixed in the latest version. Thanks, Tom Responsible-Changed-From-To: apbianco->java-hacker Responsible-Changed-By: apbianco Responsible-Changed-When: Fri Aug 20 00:33:57 1999 Responsible-Changed-Why: Changed to `libgcj' category. State-Changed-From-To: open->feedback State-Changed-By: tromey State-Changed-When: Thu Sep 2 19:05:48 1999 State-Changed-Why: I think this bug is fixed. Can you please verify so I can close the PR? State-Changed-From-To: feedback->closed State-Changed-By: tromey State-Changed-When: Thu Sep 2 19:38:17 1999 State-Changed-Why: We've done all we can do. The remaining problems are in libtool -- which we'll update as soon as a new one is released. >Unformatted:
reply other threads:[~2000-12-20 12:22 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990809015840.11284.qmail@egcs.cygnus.com \ --to=david.billinghurst@riotinto.com.au \ --cc=java-gnats@sourceware.cygnus.com \ /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: linkBe 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).