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: Wed, 11 May 2022 09:10:39 +0100	[thread overview]
Message-ID: <CAH6eHdS0dFaou7RC_WzfiRS7_BVr+Xg-UfAhqgsCJ4nSHOWjMg@mail.gmail.com> (raw)
In-Reply-To: <CAEYL+X_4R9N7BWZGF+gfFUPSycwsqjFZp4Zy1SZNa2kHB_PP6g@mail.gmail.com>

It's possible you'll need to regenerate the libjava/configure script
and the libjava/tools/Makefile.in template, because since libjava was
removed from GCC the rest of the source tree was updated to use a
newer automake and autoconf:

https://gcc.gnu.org/g:22e052725189a472e4e86ebb6595278a49f4bcdd

   Update GCC to autoconf 2.69, automake 1.15.1 (PR bootstrap/82856).

Maybe it doesn't matter, if the libjava configure is self-contained.
But it's something to be aware of.

      reply	other threads:[~2022-05-11  8:10 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
2022-05-11  8:10                       ` Jonathan Wakely [this message]

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=CAH6eHdS0dFaou7RC_WzfiRS7_BVr+Xg-UfAhqgsCJ4nSHOWjMg@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).