Tux
commented
4 years ago On Sun, 17 May 2020 22:23:58 -0700, Kent Fredric notifications@github.com wrote:
Description We have developers on Gentoo testing some unusual setups, particularly:
- There is no
/usr/bin/gcc,/usr/bin/ccor/usr/bin/ar- There is no
gcc,ccorarin$PATHAR=andCC=are both defined with correct values.Under this configuration, perl .
/configurefails to detect a correctar, and later, embedsar = arinConfig_heavy.plHowever, this failure does not stop perl from compiling, but it does make ExtUtils-MakeMaker's test suite to fail in
02xs-dynamic.t, and all EUMM based XS packages generate a makefile with:AR = arAnd afterwards, assuming you installed it regardless of test failure ( or even not running tests ), this eventually leads to breaking anything that consumes
$Config{ar}expecting it to be thearused to build "Perl itself" ( which is impossible, such a thing asardidn't exist when Perl was built ).
Your case seems clear, so the question that remains is: are cc and are the only two, or is it also others, like nm and ranlib?
If we have a defined set, would this mean that we can leave everything in place until the very last step where just before we set AR to 'ar' we should check if $AR is set to anything and use that instead. In sh talk
AR=ar
→
AR=${AR:-ar}However, there is a good workaround, as long as one invokes
./configurewith:-Dar=x86_64-pc-linux-gnu-ar
Interestingly, ar is set this way under crosscompiling
(Or similar as appropriate for the target, just keep in mind this may not even be a gcc/binutils ar, but one provided by the llvm project)
Then it JustWorks:
- The aformentioned MakeMaker tests pass
- No new test failures occur
- Subsequent EUMM XS builds have a valid value for
AR =- Large volumes of EUMM XS builds then work
So it seems this is just an inadequacy in Config not detecting AR appropriately, and also not bailing as appropriate when it would generate a bogus configuration.
Perl configuration
kentfredric
Description We have developers on Gentoo testing some unusual setups, particularly:
/usr/bin/gcc,/usr/bin/ccor/usr/bin/argcc,ccorarin$PATHAR=andCC=are both defined with correct values.Under this configuration, perl .
/configurefails to detect a correctar, and later, embedsar = arinConfig_heavy.plHowever, this failure does not stop perl from compiling, but it does make ExtUtils-MakeMaker's test suite to fail in
02xs-dynamic.t, and all EUMM based XS packages generate a makefile with:And afterwards, assuming you installed it regardless of test failure ( or even not running tests ), this eventually leads to breaking anything that consumes
$Config{ar}expecting it to be thearused to build "Perl itself" ( which is impossible, such a thing asardidn't exist when Perl was built ).However, there is a good workaround, as long as one invokes
./configurewith:(Or similar as appropriate for the target, just keep in mind this may not even be a gcc/binutils ar, but one provided by the llvm project)
Then it JustWorks:
AR =So it seems this is just an inadequacy in Config not detecting AR appropriately, and also not bailing as appropriate when it would generate a bogus configuration.
Perl configuration