From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa1-x31.google.com (mail-oa1-x31.google.com [IPv6:2001:4860:4864:20::31]) by sourceware.org (Postfix) with ESMTPS id 8604F385DC21 for ; Tue, 10 May 2022 07:23:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8604F385DC21 Received: by mail-oa1-x31.google.com with SMTP id 586e51a60fabf-edf3b6b0f2so16901730fac.9 for ; Tue, 10 May 2022 00:23:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ytLnwsxRovQ6Ihjulk3kXtv8N6ElMIJIDYt81ucJMgE=; b=29/mvOyTdsaW5D+tATb9STMD+2cUVCkNb5YCfVw5je4nFtfp0yzfWkVx0dq9UpKGl1 j41g97CV+pqeSi2Ib7G8rC71+oq9QpLEOT8GOCycnBoGBuTFMyxFSt9K8ZPC4H5CDkfg LfsAC87j8zduA7WAJ5kDxeeDZiDSz0cypRNKyuLdZiYnm/ZeXujOn0UI8jLNFCo6DaIW zrehb8mSLeGrC+hJeaEG+WOEPR7a1vFY1R6aXG2tTQeqq03uQr44gFtz3xOjXVowDVFR 72HWrTYQLUugTCuusuXCgpCvn+NUnvbW+PAo8DKq+oLmRGFyQoygRiHEwaidmMwwR6wN VpIw== X-Gm-Message-State: AOAM531r+i1YwjL9HCAXL8bB2qk0lAR7i32CQ5iqYHR3mAo4kfF7JKgA /EC/OBehxApp6AxAlzS2oRjTl/8DnHDz03n/TVcPHxj0 X-Google-Smtp-Source: ABdhPJx6RfG+EddlhpJme/HvLMCtWeVOi/z5As6B5ON0KPYVCtJzkg7dpZ1+CkVZSXCXum0//Z/YBsHaCOCtBRjv58E= X-Received: by 2002:a05:6871:4216:b0:ee:13d0:2afb with SMTP id li22-20020a056871421600b000ee13d02afbmr10941237oab.250.1652167436143; Tue, 10 May 2022 00:23:56 -0700 (PDT) MIME-Version: 1.0 References: <4d4d2db210a3f181e0114d2670a7918826957900.camel@xry111.site> <8f8fb7611632ff388659b1da3500abc181da97c2.camel@xry111.site> In-Reply-To: <8f8fb7611632ff388659b1da3500abc181da97c2.camel@xry111.site> From: Zopolis0 Date: Tue, 10 May 2022 17:23:45 +1000 Message-ID: Subject: Re: libjava configure fails on finding no C compiler in $PATH despite gcc being present To: Xi Ruoyao Cc: gcc-help@gcc.gnu.org X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2022 07:23:59 -0000 The code is public: https://github.com/Zopolis4/gcj, I posted it a while ago in an different question but presumably nobody saw that because there were no replies iirc. If I should post it in each question then I'll do that. I'd welcome help from GCC hackers and people interested in java, but this list is the best way I can think of to contact them, and it feels rude to randomly email someone who I've never met before and ask for help, as opposed to submitting a question to a dedicated question mailing list. In regards to the issue, I am running ./configure from a seperate empty directory outside of the gcc tree (../gcj/configure --enable-languages=java) 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. On Tue, 10 May 2022 at 17:11, Xi Ruoyao wrote: > 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 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 > School of Aerospace Science and Technology, Xidian University >