public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
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: Tue, 17 May 2022 09:27:15 +0100	[thread overview]
Message-ID: <d5d2c486-0a50-36aa-b128-dee4da822a16@redhat.com> (raw)
In-Reply-To: <CAEYL+X9bPXYDDhBgtFky26TJ4USJqN_F74+JG=bfHF79RQQ=Lw@mail.gmail.com>

On 5/17/22 07:12, Zopolis0 via Gcc-help 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.

So look at the output of the compilation, look at the include paths in the
compile command that failed, and see what's wrong. We can't tell from this
tiny snippet.

-- 
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


  reply	other threads:[~2022-05-17  8:27 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 [this message]
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=d5d2c486-0a50-36aa-b128-dee4da822a16@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).