public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/27860] [4.2 Regression] build failure on m68k: error: 'ffi_closure' does not name a type
Date: Fri, 02 Jun 2006 02:25:00 -0000 [thread overview]
Message-ID: <20060602022556.23603.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27860-12387@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from pinskia at gcc dot gnu dot org 2006-06-02 02:25 -------
(In reply to comment #2)
> I'm CCing Andreas Schwab since he apparently ported ffi to m68k. I noticed
> that the part of the code that produces the error is within an ifdef
> USE_LIBFFI, so possibly disabling ffi on m68k would allow it to compile. But
> maybe the real fix would be to update ffi on m68k or something. Maybe Andreas
> can take a look and/or comment.
libffi should work on m68k. It might be closures have not been ported to m68k
which means INTERPRETER should be false. (This is all from memory).
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |java-prs at gcc dot gnu dot
| |org
Summary|build failure on m68k: |[4.2 Regression] build
|error: 'ffi_closure' does |failure on m68k: error:
|not name a type |'ffi_closure' does not name
| |a type
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27860
next parent reply other threads:[~2006-06-02 2:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-27860-12387@http.gcc.gnu.org/bugzilla/>
2006-06-02 2:25 ` pinskia at gcc dot gnu dot org [this message]
2006-06-02 2:26 ` [Bug libgcj/27860] " pinskia at gcc dot gnu dot org
2006-06-04 18:35 ` schwab at suse dot de
2006-06-05 14:08 ` tromey at gcc dot gnu dot org
2006-06-05 15:03 ` schwab at suse dot de
2006-06-05 18:58 ` tbm at cyrius dot com
2006-06-05 19:05 ` schwab at suse dot de
2006-06-05 19:59 ` tromey at gcc dot gnu dot org
2006-06-05 20:02 ` tbm at cyrius dot com
2006-06-05 20:45 ` tbm at cyrius dot com
2006-06-05 21:21 ` schwab at gcc dot gnu dot org
2006-06-05 21:36 ` schwab at suse dot de
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=20060602022556.23603.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).