Cosimo,
The more I look at this, the more I wonder whether the test failure in
111-auto_gcc-01.t (reported below) has anything to do with the presence
or absence of gdbm on one's OS or whether one's Perl was build with gdbm
or not.
>
> --------------8<----------------------------
> [EMAIL PROTECTED]:~/Desktop/src/parrot$ TEST_VERBOSE=1 perl
> t/configure/111-auto_gcc-01.t
> 1..12
> ok 1 - use config::init::defaults;
> ok 2 - use config::auto::gcc;
> ok 3 - init::defaults constructor returned defined value
> ok 4 - The object isa init::defaults
> ok 5 - init::defaults has description
> ok 6 - init::defaults runstep() returned defined value
> ok 7 - auto::gcc constructor returned defined value
> ok 8 - The object isa auto::gcc
> ok 9 - auto::gcc has description
> Linker failed (see test.ldo) at lib/Parrot/Configure/Step.pm line 525
> Parrot::Configure::Step::cc_build() called at config/auto/gcc.pm
> line 42
> auto::gcc::_probe_for_gcc() called at config/auto/gcc.pm line 35
> auto::gcc::runstep('auto::gcc=HASH(0x83d9194)',
> 'Parrot::Configure=HASH(0x82e7a04)') called at
> t/configure/111-auto_gcc-01.t line 40
> # Looks like you planned 12 tests but only ran 9.
> # Looks like your test died just after 9.
> [EMAIL PROTECTED]:~/Desktop/src/parrot$
> --------------8<----------------------------
There's nothing in this error message that makes any reference to gdbm.
I looked at the code in config/init/defaults.pm and
lib/Parrot/Configure/Step.pm that is relevant here, and I find no
reference to gdbm there. In particular, I can't figure out why the
presence of gdbm when your Perl 5 was built should cause a failure in a
test for gcc.
Is it possible that this test failure could be due to causes that have
nothing whatsoever to do with gdbm?
kid51
