# New Ticket Created by Andy Dougherty
# Please include the string: [perl #47391]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=47391 >
I decided to try to give parrot a spin again today, and ran into some
problems in the t/configure/1* tests. Specifically, the following all
failed with similar symptoms:
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/configure/115-auto_warnings.t 1 256 4 1 25.00% 4
t/configure/124-auto_alignptrs-05 1 256 11 1 9.09% 10
t/configure/146-auto_snprintf-01. 255 65280 9 0 0.00% ??
A typical failure looks like this:
t/configure/124-auto_alignptrs-05............
# Failed test (t/configure/124-auto_alignptrs-05.t at line 49)
# 'Linker failed (see test.ldo) at
lib/Parrot/Configure/Step.pm line 525
# Parrot::Configure::Step::cc_build() called at config/auto/alignptrs.pm
line 59
# auto::alignptrs::runstep('auto::alignptrs=HASH(0x3b0054)',
'Parrot::Configure=HASH(0x2d2270)') called at
t/configure/124-auto_alignptrs-05.t line 47
# eval {...} called at t/configure/124-auto_alignptrs-05.t line 47
# '
# doesn't match '(?-xism:Can't determine alignment)'
# Looks like you failed 1 test of 11.
dubious
Test returned status 1 (wstat 256, 0x100)
After looking into it some, the problem seems to be that these tests
rely on init::defaults. That simply won't work if the configuration
being used to build parrot is sufficiently different from that which
was used to build perl. That's what happened to me in this case.
This probably doesn't show up often because nearly everyone building
parrot right now uses the same configuration as was used to build perl.
However, that's not necessarily the norm. Vendors such as Sun supply
a perl pre-built with their compiler, but many end users have gcc
installed instead.
If a test for a configuration step relies on certain Config values, the
only correct approach is to use the Config values determined by
Configure.pl. There is no guarantee that the init::defaults values will
work. They may well have been changed, either by the user (via --ask or
command line overrides) or by the Configure.pl system itself.
--
Andy Dougherty [EMAIL PROTECTED]
