Alex Suykov

Current defaults are `-fwrapv -fno-strict-aliasing`. I skimmed over the mainline Configure, it does not look like they are passing anything else either. If you did not pass `-fno-strict-aliasing`, try adding...

For issues like this, it would be really nice to have config.sh from the failing cross build, and also the one from a successful build if available. It's very difficult...

Quick check to verify that: open config.log, and search for "variadic". There will be two check in case of a cross build, the first one for host-miniperl and the second...

Ah, I see. This one is easy to fix, there's no need to have `\n` there at all, it's completely irrelevant for the test. I'll try running the rest with...

Removed all `\n` uses. That `trnl` value isn't even used anywhere. And yeah xconfig.h is a host-specific file that should not be packaged.

Since it happens in `make install`, then yeah deleting it after the fact is probably the best option. The alternative is patching `installperl`. perl.h includes `xconfig.h` in place of `config.h`...

What exactly fails in the test suite? Tests never use config.sh directly for that purpose, they load Config_heavy.pl via Config.pm, which is generated from config.sh. The script that generates Config_heavy.pl...

Preliminary patch: https://github.com/arsv/perl-cross/tree/extensions Works for me so far, but I'll try running it a bit more with less common options. This issue is mostly limited to tests but the fix...

Download the modules you need, and unpack them into cpan/ before running configure. Check existing modules there to see how directory structure should look like. For compiled (XS) modules, you...

No, configure doesn't really handle dependencies even for the core modules. Modules from cpan/ will be built in alphabetical order their directories. It's up to you to download all soft...