From: Zopolis0 <creatorsmithmdt@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
Date: Wed, 11 May 2022 13:53:47 +1000 [thread overview]
Message-ID: <CAEYL+X9wenf1hUs++iuFe=asbGEv5QUoZLH4UaCbMGGrDbygdQ@mail.gmail.com> (raw)
In-Reply-To: <CAEYL+X9X7R+rZqWAAW=WsRF5OWOdon2mXD9k29BfKyf=igH3Kw@mail.gmail.com>
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@gmail.com> 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@xry111.site> 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@xry111.site>
>> School of Aerospace Science and Technology, Xidian University
>>
>
next prev parent reply other threads:[~2022-05-11 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 0:18 Zopolis0
2022-05-10 5:51 ` Xi Ruoyao
2022-05-10 6:55 ` Zopolis0
2022-05-10 7:11 ` Xi Ruoyao
2022-05-10 7:23 ` Zopolis0
2022-05-10 8:10 ` Jonathan Wakely
2022-05-10 8:11 ` Jonathan Wakely
2022-05-10 10:56 ` Zopolis0
2022-05-10 11:01 ` Xi Ruoyao
2022-05-10 11:18 ` Zopolis0
2022-05-11 3:53 ` Zopolis0 [this message]
2022-05-11 5:59 ` Zopolis0
2022-05-11 6:35 ` Zopolis0
2022-05-11 8:10 ` Jonathan Wakely
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+X9wenf1hUs++iuFe=asbGEv5QUoZLH4UaCbMGGrDbygdQ@mail.gmail.com' \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=xry111@xry111.site \
/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).