Open lenticularis39 opened 3 years ago
Does perl in t2/trunk currently even cross compile? ;-) Decades ago this was by design as more did usually not cross compile, maybe now with the restructured 1 and 2 cross stages we could build a more full features perl in 2-perl? If anyone using Perl wants to give modifying the perl.{desc,conf} a try for that and post the result it would be helpful.
It doesn't have the CROSS flag set, but unlike some time ago Perl itself cross compiles fine, it's only the bundled modules which fail. Having Perl cross compiled would help, because it's a common package which takes some time to build on older systems.
I'll probably have a look at it myself when I get to it, I reported the issue mostly to track it for myself :)
IIRC I removed the CROSS flag recently as it did not cross build for me, and I did not wanted bootstraps to error out on perl. So from my experience Perl used to cross-build as patched or configured in t2 until recently. Though this native mini perl hack needed some re-diffing every other year anyways ;-)
After investigating the log it's clear that it's trying to execute the cross-compiled perl binary at some point:
./perl: 1: Syntax error: ")" unexpected
It's quite unbelievable that after so many years Perl still hasn't be able to make the build system cross-compile aware, requiring patches or hacks.
When cross-compiling Perl (tested on x86_64 -> hppa, might happen on other archs), the resulting package is much smaller than when native compiling:
After examining the flists it's apparent that many modules are missing from the cross-compiled package (maybe a gcc cross compiling problem?), for example Scalar/Util.pm.
The full flists are attached to the issue, along with the cross compilation build log.
cross.flist.log cross.log.gz native.flist.log