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@xxxxxxxxxxx> 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@xxxxxxxxxxx> School of Aerospace Science and Technology, Xidian University
