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 <xry111@xxxxxxxxxxx> 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 <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 >
