public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Zopolis0 <creatorsmithmdt@gmail.com>
Cc: Xi Ruoyao <xry111@xry111.site>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
Date: Tue, 10 May 2022 09:11:14 +0100	[thread overview]
Message-ID: <CAH6eHdQn6Ye9KM1LZ=MGb1F25jkkL7cnHtQy9uaX6tktVp+=7w@mail.gmail.com> (raw)
In-Reply-To: <CAEYL+X90BPFD-b6Wzqy47mu=3FAked4Q_4yku+ozWOef8xpLtw@mail.gmail.com>

On Tue, 10 May 2022 at 08:24, Zopolis0 via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
> To my knowledge the build system invokes the configure script in libjava as
> it does all the others, I think the issue is within the script itself. How
> would I check the way it is running the configure script? It dosent seem to
> show up in the build output.

Each directory in the build tree has a config.log which is created by
the configure script for that directory.

At the top of config.log it shows how configure was run.

  parent reply	other threads:[~2022-05-10  8:11 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 [this message]
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
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='CAH6eHdQn6Ye9KM1LZ=MGb1F25jkkL7cnHtQy9uaX6tktVp+=7w@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=creatorsmithmdt@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --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).