From: Andrew Haley <aph@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Re: fatal error: ffi.h: No such file or directory despite libffi being enabled
Date: Mon, 16 May 2022 13:01:24 +0100 [thread overview]
Message-ID: <425f7f05-f9f8-1240-5589-242b164f286d@redhat.com> (raw)
In-Reply-To: <CAEYL+X9uXHKvHp-LBQkvRO7C5n+fdjpeL5-wa53zUj-2_xd_ag@mail.gmail.com>
On 5/16/22 02:06, Zopolis0 via Gcc-help wrote:
> While attempting to compile gcj on my mster branch (
> https://github.com/Zopolis4/gcj/tree/mster) , the compilation fails because
> several files within libjava are unable to include ffi.h because they
> cannot find it.
> In file included from ../../../../gcj/libjava/defineclass.cc:24:
> ../../../../gcj/libjava/include/java-interp.h:40:10: fatal error: ffi.h: No
> such file or directory
> 40 | #include <ffi.h>
> | ^~~~~~~
> This is despite, as far as I can tell, the compilation of libffi being
> enabled as part of libjava in makefile.def.
We only ever built libjava as part of a whole-GCC build. The libjava
directory isn't intended to be built on its own. Please build the whole
GCC tree using the top-level makefile and it'll work, then you can
extract whatever built pieces you need.
--
Andrew Haley (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
next prev parent reply other threads:[~2022-05-16 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 1:06 Zopolis0
2022-05-16 12:01 ` Andrew Haley [this message]
2022-05-17 6:12 ` Zopolis0
2022-05-17 8:27 ` Andrew Haley
2022-05-17 12:29 ` Zopolis0
2022-05-17 12:31 ` Zopolis0
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=425f7f05-f9f8-1240-5589-242b164f286d@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@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).