On Mon, Oct 22, 2012 at 03:24:52PM +0200, [email protected] wrote:
> Do you know the exact $Config{archname} for sparc and powerpc, then I will
> only enable this for these architectures
in Debian these values are:
sparc: sparc-linux-gnu-thread-multi-64int
powerpc: powerpc-linux-gnu-thread-multi-64int
There was a suggestion in #debian-perl to inspect $Config{ccflags} for
-m32 and use it only if present, or use $Config{ccflags} directly, but I
don't really know enough about these things or why Embperl does things
the way it does to really have an opinion on this.
Florian
> > -----Original Message-----
> > From: Florian Schlichting [mailto:[email protected]]
> > Sent: Saturday, October 20, 2012 9:53 PM
> > To: Gerald Richter - ECOS; [email protected]
> > Subject: build failures on arm, mips: -m32 not available
> >
> > Hi,
> >
> > I'm forwarding Debian bug http://bugs.debian.org/691032 - Embperl 2.5.0
> > RC2 fails to build on armel/armhf, mips/mipsel, s390 due to -m32 not being
> > available on those platforms as a valid gcc flag.
> >
> > The use of -m32 in Makefile.PL was introduced in Embperl 2.4.0 along with
> > $perl32bit, to have Embperl compile as a 32 bit application on a 64 bit
> > system
> > if Perl itself was compiled as a 32 bit application. The patch used in
> > Debian (as
> > referenced in the Debian bug) simply removes both uses of -m32; but then
> > Debian doesn't compile Perl as a 32bit application on 64 bit architectures.
> > Perhaps everybody would be happy if something like $Config{archname} =~
> > /x86_64/ was checked in addition to $Config{ptrsize} == 4 for $perl32bit to
> > be
> > set? (but note that in addition to i386/amd64, also sparc and powerpc
> > architectures support
> > -m32...)
> >
> > Florian
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
