From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa1-x32.google.com (mail-oa1-x32.google.com [IPv6:2001:4860:4864:20::32]) by sourceware.org (Postfix) with ESMTPS id A0F1F3858D3C for ; Tue, 17 May 2022 12:31:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A0F1F3858D3C Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-f17f1acffeso11407939fac.4 for ; Tue, 17 May 2022 05:31:50 -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=6dXuIs3UcQcc0go4jW8TecI0Hd0kn2UOmsrvmuzyX4c=; b=dq1F6VqM4Ge7IVaFd3ybfQKlRWN0Vd754HXCEBYpZ8OVU7s+20KGBUFirY59WStzQ+ E11O+ik8/MUJRWSbcYBAL6dxbr49ZaI5KtI+rgK+grcrj3wZeen0qdsZay1hADU+bjgd S9XmA9HoyWF/rcYT9HIqWhhv9nooN9GfUhXXAqBvqPOeniY4+5L7Fnhp60jMUfT0pXhO DdUVQsrBNo1jRAfmXAhYy6kNjIpirvPvTsch6xII4lMzpfchGqZHOg7wLQYiqxrHZ8U6 4qi6qJIe3BDwVtqwC/4zwOHegqqQduIp1OM3R50U+jdEmHOhHw/ccYWtT7cwjYvKlLtX /90A== X-Gm-Message-State: AOAM533h8VQDBwgN+1Ecv6dWjX7nxug/yUz+MHvZptUmZKkRH05hByhL 1nxwppEj22AmWQQyJSc04mqvXNjII7mnyBfQQDwO+p3O8Lc= X-Google-Smtp-Source: ABdhPJyO+hYf20ruUrNy3WmW6mWhy0ec0enDp0Y/b93ShP6sOqxwTLq4PvcuorA3g6apHjdcEDPenbD2CH24gd+Dpwk= X-Received: by 2002:a05:6870:e245:b0:de:9321:9ea3 with SMTP id d5-20020a056870e24500b000de93219ea3mr12314467oac.79.1652790709798; Tue, 17 May 2022 05:31:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Zopolis0 Date: Tue, 17 May 2022 22:31:35 +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=1.0 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-Level: * 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:31:52 -0000 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 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 > 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. >>> >>