[Bug java/30591] Cross build fails because native gcj needed to build ecjx
--- Comment #6 from daney at gcc dot gnu dot org 2007-05-16 21:10 --- Marking as FIXED as it now works for me *if* I use a current native GCC to build the cross compiler. I am prepering a documentation patch that explains my interpretation of the requirements. -- daney at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Target Milestone|--- |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591
[Bug java/30591] Cross build fails because native gcj needed to build ecjx
--- Comment #5 from mtrudel at gmx dot ch 2007-04-25 07:17 --- You write it needs a host version of gcj, your host is i686-pc-linux-gnu and configure looks for i686-pc-linux-gnu-gcj? Seems correct to me? What gcj should be searched for? The only problem I'm currently aware of is that the compilation of ecj.jar uses -findirect-dispatch. This fails for static compilations since indirect-dispatch doesn't work anymore with such compilations since some bc abi (or whatever) changes. It can easily be fixed by modifying libgcj.a.spec. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591
[Bug java/30591] Cross build fails because native gcj needed to build ecjx
--- Comment #3 from tromey at gcc dot gnu dot org 2007-04-25 01:12 --- Is this still a problem? I thought it was ironed out a while ago. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591
[Bug java/30591] Cross build fails because native gcj needed to build ecjx
--- Comment #4 from ddaney at avtrex dot com 2007-04-25 01:16 --- Subject: Re: Cross build fails because native gcj needed to build ecjx tromey at gcc dot gnu dot org wrote: --- Comment #3 from tromey at gcc dot gnu dot org 2007-04-25 01:12 --- Is this still a problem? I thought it was ironed out a while ago. I have not tested it recently. I will try to test again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591
[Bug java/30591] Cross build fails because native gcj needed to build ecjx
--- Comment #1 from daney at gcc dot gnu dot org 2007-01-25 23:12 --- This is actually contains the error from the build output this time: i686-pc-linux-gnu-gcj -o ecjx -findirect-dispatch --main=org.eclipse.jdt.internal.compiler.batch.GCCMain ../../../trunk/libjava/.././libjava/../ecj.jar make[3]: i686-pc-linux-gnu-gcj: Command not found make[3]: *** [ecjx] Error 127 make[3]: Leaving directory `/home/daney/gccsvn/mipsel-trunk/mipsel-linux/libjava' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/daney/gccsvn/mipsel-trunk/mipsel-linux/libjava' make[1]: *** [all-target-libjava] Error 2 make[1]: Leaving directory `/home/daney/gccsvn/mipsel-trunk' make: *** [all] Error 2 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591
[Bug java/30591] Cross build fails because native gcj needed to build ecjx
--- Comment #2 from tromey at gcc dot gnu dot org 2007-01-26 02:23 --- FWIW I don't think we want to fail outright if no suitable gcj is found. The whole business with compiling and installing ecj.jar is a convenience, not a strict necessity. The user can always make his own ecj1 somehow (e.g, I use a shell script). So one idea would be to look for a gcj for the build machine, and if not found, disable compilation of ecjx. What do you think? -- tromey at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|-00-00 00:00:00 |2007-01-26 02:23:25 date|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30591