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 16:35:26 +1000 [thread overview]
Message-ID: <CAEYL+X_4R9N7BWZGF+gfFUPSycwsqjFZp4Zy1SZNa2kHB_PP6g@mail.gmail.com> (raw)
In-Reply-To: <CAEYL+X_ZyuP+xQp7DReMKGy-GRRZ6bmPMzWZb_X8AbJrgf_LEA@mail.gmail.com>
Never mind, the issue when away when I deleted libjava/libltdl, which
wasn't really necessary as far as I can tell because libltdl ships with
libtool which is already a dependency for compiling gcc.
On Wed, May 11, 2022 at 3:59 PM Zopolis0 <creatorsmithmdt@gmail.com> wrote:
> All of the relevant M4sh Shell Functions in other configure scripts in gcc
> were either added along with the rest of the directory or date back
> to 22e052725189a472e4e86ebb6595278a49f4bcdd, which did not make notable
> modifications to the configure.ac scripts, which leads me to believe that
> there might be something overriding or blocking the creation of these
> functions in libjava/configure.ac and libjava/libltdl/configure.ac. I
> also have a suspicion that the reason classpath works is that it was
> designed to be a standalone library from gcc.
>
>>
next prev parent reply other threads:[~2022-05-11 6:35 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
2022-05-11 5:59 ` Zopolis0
2022-05-11 6:35 ` Zopolis0 [this message]
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+X_4R9N7BWZGF+gfFUPSycwsqjFZp4Zy1SZNa2kHB_PP6g@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).