Invalid use of -m32 on certain targets

Severin Gehwolf sgehwolf at redhat.com
Fri Apr 13 12:16:28 UTC 2018


On Fri, 2018-04-13 at 13:17 +0200, Severin Gehwolf wrote:
> On Thu, 2018-04-12 at 18:56 +0200, Magnus Ihse Bursie wrote:
> > > 12 apr. 2018 kl. 15:49 skrev John Paul Adrian Glaubitz <glaubitz at physik.fu-berlin.de>:
> > > 
> > > Hi!
> > > 
> > > I have been playing around with Zero on new (old) architectures and one
> > > of them is hppa, which needs some additional work due to its stack growing
> > > from bottom to top but that's another story.
> > > 
> > > Anyway, adding hppa to platform.m4 and running configure results in the
> > > following error message:
> > > 
> > > configure:35290: checking whether the C compiler works
> > > configure:35312: /usr/bin/hppa-linux-gnu-gcc -m32    -m32   conftest.c  >&5
> > > hppa-linux-gnu-gcc: error: unrecognized command line option '-m32'
> > > hppa-linux-gnu-gcc: error: unrecognized command line option '-m32'
> > > configure:35316: $? = 1
> > > configure:35354: result: no
> > > configure: failed program was:
> > > 
> > > Didn't we recently have the discussion about which target gcc versions
> > > understand "-m32" and which don't? Apparently, someone thought hppa's
> > > gcc supports that option but apparently it doesn't.
> > > 
> > > Was there any conclusion on this discussion? I remember that some
> > > people mentioned that the current situation is not ideal.
> > 
> > I agree. It's not ideal, and should be fixed. It's on my todo list
> > but keep sinking to the bottom. If you want, you can open a bug on it
> > and I just might get around to it a bit quicker. :)
> 
> I've just attempted "configure" on s390 and here is what I get:
> configure:35266: checking whether the C compiler works
> configure:35288: /usr/bin/gcc -m32    -m32   conftest.c  >&5
> gcc: error: unrecognized command line option '-m32'
> gcc: error: unrecognized command line option '-m32'
> configure:35292: $? = 1
> configure:35330: result: no
> configure: failed program was:
> > /* confdefs.h */
> > #define PACKAGE_NAME "OpenJDK"
> > #define PACKAGE_TARNAME "openjdk"
> > #define PACKAGE_VERSION "jdk9"
> > #define PACKAGE_STRING "OpenJDK jdk9"
> > #define PACKAGE_BUGREPORT "build-dev at openjdk.java.net"
> > #define PACKAGE_URL "http://openjdk.java.net"
> > /* end confdefs.h.  */
> > 
> > int
> > main ()
> > {
> > 
> >   ;
> >   return 0;
> > }
> 
> configure:35335: error: in `/jdk-hs':
> configure:35337: error: C compiler cannot create executables
> 
> Indeed:
> <mock-chroot> sh-4.2# gcc -m32 conftest.c 
> gcc: error: unrecognized command line option ‘-m32’
> <mock-chroot> sh-4.2# echo $?
> 1
> <mock-chroot> sh-4.2# gcc conftest.c
> <mock-chroot> sh-4.2# echo $?
> 0 
> 
> This must have broken recently :( I'll take a look. As it's preventing
> me to test JDK-8201495
> 
> Is there a bug for this already?

Here is one:
https://bugs.openjdk.java.net/browse/JDK-8201536

Cheers,
Severin

> Thanks,
> Severin
> 
> 
> > /Magnus
> > 
> > > 
> > > Adrian
> > > 
> > > -- 
> > > .''`.  John Paul Adrian Glaubitz
> > > : :' :  Debian Developer - glaubitz at debian.org
> > > `. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
> > >  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
> > > 
> > 
> > 


More information about the build-dev mailing list