public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bryce@albatross.co.nz
To: java-gnats@sourceware.cygnus.com
Subject: libgcj/1246: link failure with multilib and/or "--disable-static" builds
Date: Wed, 20 Dec 2000 12:23:00 -0000 [thread overview]
Message-ID: <20000505120325.5008.qmail@sourceware.cygnus.com> (raw)
>Number: 1246
>Category: libgcj
>Synopsis: link failure with multilib and/or "--disable-static" builds
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: tromey
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Dec 20 12:18:14 PST 2000
>Closed-Date:
>Last-Modified: Fri May 5 09:20:00 PDT 2000
>Originator: Bryce McKinlay
>Release: unknown-1.0
>Organization:
>Environment:
linux
>Description:
libgcj build fails during linking of jv-convert with missing
symbol errors for libffi.
The problem is related the following line in the makefile:
libffi_files = `$(AR) t ../libffi/.libs/libffi.a 2>/dev/null | sed 's/\.o/\.lo/g'
| sed 's/^/..\/libffi\//g'`
libffi.a does not exist in a "--disable-static" build.
>How-To-Repeat:
>Fix:
Build libffi as a shared library?
Hack libffi's Makefile so that libffi.a is allways built?
>Release-Note:
>Audit-Trail:
Formerly PR libgcj/221
From: Tom Tromey <tromey@cygnus.com>
To: bryce@albatross.co.nz
Cc: java-gnats@sourceware.cygnus.com, Anthony Green <green@cygnus.com>
Subject: Re: libgcj/221: link failure with multilib and/or "--disable-static" builds
Date: Fri, 5 May 2000 09:17:07 -0700 (PDT)
Bryce> Build libffi as a shared library?
Bryce> Hack libffi's Makefile so that libffi.a is allways built?
We can solve this by building libffi as a convenience library.
Then we let libtool do the hard work.
But then we run up against the automake version problem.
Grr.
Tom
>Unformatted:
next reply other threads:[~2000-12-20 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 12:23 bryce [this message]
2001-12-02 22:02 tromey
2001-12-02 22:06 tromey
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=20000505120325.5008.qmail@sourceware.cygnus.com \
--to=bryce@albatross.co.nz \
--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: 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).