This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: multilib fixes for libjava
Andrew,
Unfortunately the situation is that Darwin PPC is the only
architecture to easily test this on. The multi.m4 changes were
added to fix the problem of building 64-bit binaries on a 32-bit
processor. Since Darwin is the only architecture that does that
at the moment (build 32-bit by default and 64-bit as the secondary),
we can only reproduce this problem on a G4. If I understand Geoff's
emails correctly, he actually only tested his multi.m4 related
changes on Darwin Intel and did not include java in the language
set. I would appear to be the first person to try to do the multilib
builds on a G4 since his multi.m4 patches went in.
A couple observations. The proposed patch I posted does change
the location of the failure in configure. Without the proposed patch,
configure fails as...
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
If I am reading the configure script in libjava properly, I believe
we are now failing earlier in the configure script with the proposed
patch...
checking for dladdr in -ldl... yes
checking for /proc/self/exe... configure: error: cannot check for file existence when cross compiling
Is there some way I can make configure be more verbose about why this check
is failing when it is run? I am afraid I am going to have to do all the
testing myself unless we can convince Geoff to try to build java on a
G4.
Jack
ps On the postive side, we at least no my changes don't break a
standard build with the java language on a 64-bit processor. So we
just aren't totally converting configure over to use multi.m4, in
my opinion anyway.
On Mon, Nov 06, 2006 at 01:17:20PM +0000, Andrew Haley wrote:
> Jack Howarth writes:
> > I should add that the proposed patch doesn't fail to build on a G5.
> > The bootstrap and install completes as expected. So somehow this patch
> > is incomplete in implementing Geoff's use of the new multi.m4. Unfortunately
> > Geoff seems disinterested in fixing this so we will have to puzzle it
> > out on our own.
>
> OK. Well, my problem is that I have no idea what the problem is. gcj
> multilib in x86 GNU/Linux has been working more or less forever, and I
> don't know whay Darwin should have any particular difficulties.
>
> Andrew.