public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Zopolis0 <creatorsmithmdt@gmail.com>
Cc: 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 15:11:21 +0800	[thread overview]
Message-ID: <8f8fb7611632ff388659b1da3500abc181da97c2.camel@xry111.site> (raw)
In-Reply-To: <CAEYL+X-cBnRCEqDpv4jaKw6btbQDV5SRTEy7Y2mBozcL+CqK5A@mail.gmail.com>

On Tue, 2022-05-10 at 16:55 +1000, Zopolis0 wrote:
> Yeah but the issue still shows up when i do it normally, as the build
> process still runs the ./configure file in each subfirectory.
> 
> On Tue, 10 May 2022 at 15:51, Xi Ruoyao <xry111@xry111.site> wrote:
> > On Tue, 2022-05-10 at 10:18 +1000, Zopolis0 via Gcc-help wrote:
> > > I am running ./configure directly from libjava
> > 
> > Generally it's not supported by GCC building system (for each target
> > libraries, not only libjava).
> > 

Wait a minute: are you running ./configure directly in gcc source
directory when you are "doing it normally"?  No, you should make an
empty directory and run /path/to/gcc-x.y.z/configure.

If you've already done it correctly but the building system still
invokes "./configure" directly in libjava (or another subdirectory)
instead of running "/path/to/gcc-x.y.z/libjava/configure", something is
wrong in the building system.  Then we can't know why because we don't
know what you've done to GCC code.

Something you need to be aware of: if you are really doing a serious
project adding Java back to GCC, it's better to follow the FLOSS way and
publish the code somewhere.  Then it's easier to collaborate with
others.  The other people interested in Java and also experienced in
hacking GCC (forgive me if it's insulting, but it seems you are not so
familiar with GCC code to finish all the job yourself) can better help
you (I know almost nothing about Java, only able to write "Hello
world").  OTOH if you are just playing, I'll not reply anymore because
this list is for "help for building and using GCC", not "playing with
GCC".
-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

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

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=8f8fb7611632ff388659b1da3500abc181da97c2.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=creatorsmithmdt@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).