From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) by sourceware.org (Postfix) with ESMTPS id DA23C3857831 for ; Tue, 17 May 2022 12:29:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DA23C3857831 Received: by mail-oi1-x233.google.com with SMTP id j12so22075899oie.1 for ; Tue, 17 May 2022 05:29:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=4VU4K8VQX7V15N7JZLLG9tzQneWetd42BlDt9aYjjSA=; b=NpzcoMY+9gABEF0xUe5wZyvxuF1LA+30E5CO/J6/KKWlQPAFsi8GVCdSUjJCBSp6M1 Xi3uuw+oTWzH3ZYuohMBOtcLSay8D2lVnYnQP0kP9WS58RuNjTapFu+Pjc7si6Ve1Ds7 1Nml7MPyQZ4LDOQ6VFePwHyefKhutnBPieqpbfv63LtaTV6uD1MZG4X23KLzlDsOUiGt KKIa8+jp6WNMQ/xcGBTSPV5t8w1MP7OKFNSGJ5/rdLPe3evqFda70Bt3Xvvvs8gwuFZ8 kBL0xp+anYDYpdNuQt4n8P69hXTruTbjKuL688EsiwJXsqAGgHklgJ74MN+fiZgS461H En+w== X-Gm-Message-State: AOAM531S0tFhaNk8NvAGllZfjsjpDbxXwyDzqIVSPdLZBzjaFOdbdRlO G3X4XPfs6z7y/7lnZcau1eqZqPYvQDOjalicpgHKr1RrRdg= X-Google-Smtp-Source: ABdhPJyp/uxBgs8N5pIVAreYuV3lCwgKWtgT9XeBD1OJsf8gOrORdp4VxLT43nlcP46r1HC9TakkjfNhbB1GGScG5wE= X-Received: by 2002:a05:6808:2097:b0:326:6bc9:407e with SMTP id s23-20020a056808209700b003266bc9407emr15746065oiw.250.1652790586842; Tue, 17 May 2022 05:29:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Zopolis0 Date: Tue, 17 May 2022 22:29:32 +1000 Message-ID: Subject: Re: fatal error: ffi.h: No such file or directory despite libffi being enabled To: gcc-help X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2022 12:29:49 -0000 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 wrote: > That's what I was doing, with --enable-languages=java. > > On Mon, May 16, 2022 at 11:06 AM Zopolis0 > 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 >> | ^~~~~~~ >> This is despite, as far as I can tell, the compilation of libffi being >> enabled as part of libjava in makefile.def. >> >