Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Zopolis0 <creatorsmithmdt@xxxxxxxxx>
Subject: Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
Date: Wed, 11 May 2022 09:10:39 +0100
Cc: gcc-help <gcc-help@xxxxxxxxxxx>
In-reply-to: <CAEYL+X_4R9N7BWZGF+gfFUPSycwsqjFZp4Zy1SZNa2kHB_PP6g@mail.gmail.com>
References: <CAEYL+X-KgJevKBA2tAaa60FyRfM5G5cuTDwhfJm7MueX=22WuA@mail.gmail.com> <4d4d2db210a3f181e0114d2670a7918826957900.camel@xry111.site> <CAEYL+X-cBnRCEqDpv4jaKw6btbQDV5SRTEy7Y2mBozcL+CqK5A@mail.gmail.com> <8f8fb7611632ff388659b1da3500abc181da97c2.camel@xry111.site> <CAEYL+X90BPFD-b6Wzqy47mu=3FAked4Q_4yku+ozWOef8xpLtw@mail.gmail.com> <CAH6eHdQn6Ye9KM1LZ=MGb1F25jkkL7cnHtQy9uaX6tktVp+=7w@mail.gmail.com> <CAEYL+X-srd7ptwRt_ZqGy0hVoYgeZxV4bxkvw6Tor=qfe5r6LA@mail.gmail.com> <d0d3b715ac2820893e92d35297bc116645a45910.camel@xry111.site> <CAEYL+X9X7R+rZqWAAW=WsRF5OWOdon2mXD9k29BfKyf=igH3Kw@mail.gmail.com> <CAEYL+X9wenf1hUs++iuFe=asbGEv5QUoZLH4UaCbMGGrDbygdQ@mail.gmail.com> <CAEYL+X_ZyuP+xQp7DReMKGy-GRRZ6bmPMzWZb_X8AbJrgf_LEA@mail.gmail.com> <CAEYL+X_4R9N7BWZGF+gfFUPSycwsqjFZp4Zy1SZNa2kHB_PP6g@mail.gmail.com>
Reply-to: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>

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.

References:
- libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Xi Ruoyao via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Xi Ruoyao via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Jonathan Wakely via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Xi Ruoyao via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help
- Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
  - From: Zopolis0 via Gcc-help

Prev by Date: Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
Next by Date: Re: slowdown with -std=gnu18 with respect to -std=c99
Previous by thread: Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present
Next by thread: How target.md file with target.c/.cc file invoke assembly instructions
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]