On further analysis, the reason it cannot find gcc is almost certainly because it is missing certain M4sh Shell Functions, specifically the lack of "as_fn_executable_p FILE" is what is causing it to fail, although other missing functions include "as_fn_exit STATUS" and "as_fn_set_status STATUS". Curiously enough, these functions are present, although commented out, in the config.status section of configure (the libjava one). Running config.status does not replace the functions nor solve the issue. However, these functions are present in the classpath configure script, and that one works perfectly. (Note: I am working on the mster branch instead of the msterstable one: https://github.com/Zopolis4/gcj/tree/mster) On Tue, May 10, 2022 at 9:18 PM Zopolis0 <creatorsmithmdt@xxxxxxxxx> wrote: > Thanks. So, the build system is invoking it correctly, as far as I can > tell. (/home/zopolis4/gcj/libjava/configure --srcdir=../../../gcj/libjava > --cache-file=./config.cache --enable-multilib --disable-bootstrap > --disable-libstdcxx --enable-languages=c,c++,java,lto > --program-transform-name=s,y,y, --disable-option-checking > --with-target-subdir=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu > --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --disable-static) > > On Tue, May 10, 2022 at 9:01 PM Xi Ruoyao <xry111@xxxxxxxxxxx> wrote: > >> On Tue, 2022-05-10 at 20:56 +1000, Zopolis0 wrote: >> > By the build tree do you mean the directory I'm running configure >> > from? If so, then no libjava directory is present despite the libjava >> > configure script certainly running during the build process. >> >> It should be in x86_64-pc-linux-gnu (or whatever triplet for your >> platform) directory, along with other target libraries (for eg >> libstdc++-v3). If not, something is wrong. >> >> -- >> Xi Ruoyao <xry111@xxxxxxxxxxx> >> School of Aerospace Science and Technology, Xidian University >> >
