From: Zopolis0 <creatorsmithmdt@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: fatal error: ffi.h: No such file or directory despite libffi being enabled
Date: Tue, 17 May 2022 22:31:35 +1000 [thread overview]
Message-ID: <CAEYL+X8moe3HYX4EUVHvXgKU2M9NQQc42DoBkr1ZwO01=NJ_Fg@mail.gmail.com> (raw)
In-Reply-To: <CAEYL+X9ha+NFoLg=fznghBe6m2Wi-cxvxLurLtKtM9aErHxUrA@mail.gmail.com>
Ah. On further inspection, the reason libffi is not compiled is most likely
because it is disabled in the initial configure:
*** This configuration is not supported in the following subdirectories:
gnattools gotools target-libada target-libphobos target-zlib
target-libbacktrace target-libgfortran target-libgo target-libffi
target-libobjc target-liboffloadmic
(Any other directories should still work fine.)
On Tue, May 17, 2022 at 10:29 PM Zopolis0 <creatorsmithmdt@gmail.com> wrote:
> Alright so looking at the include paths passed to it via the command line,
> it uses -I../../../../gcj/libjava/../libffi/include, which seems to be
> correct from what I can tell, it's definitely the right path to libjava,
> and looks to be the right path to libffi. However, in the build directory,
> grepping for libffi only reveals results in documentation and makefiles,
> and I cannot find any libffi directory. I presume this is because it is
> compiling libjava before libffi for some reason? In the libffi include
> directory there's no ffi.h, only a ffi.h.in, so it looks like it needs to
> be generated first. Is there anywhere within the sources that sets what
> order things are compiled in?
>
> On Tue, May 17, 2022 at 4:12 PM Zopolis0 <creatorsmithmdt@gmail.com>
> wrote:
>
>> That's what I was doing, with --enable-languages=java.
>>
>> On Mon, May 16, 2022 at 11:06 AM Zopolis0 <creatorsmithmdt@gmail.com>
>> 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.
>>>
>>
prev parent reply other threads:[~2022-05-17 12:31 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
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 [this message]
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='CAEYL+X8moe3HYX4EUVHvXgKU2M9NQQc42DoBkr1ZwO01=NJ_Fg@mail.gmail.com' \
--to=creatorsmithmdt@gmail.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).