On Mon Apr 16 16:36:56 2007, [EMAIL PROTECTED] wrote:
> I ran Makefile.PL on a random windows box which hasn't had its
> compiler
> installed correctly yet. Rather than emitting an error message about
> how it couldn't find my compiler, it apparently passed the test, and
> then crashed multiple times later on:
>
>
[snip]
> Checking
> MANIFEST.....................................................done.
> Setting up Configure's default
> values.................................done.
> Setting up installation
> paths.........................................done.
> Tweaking settings for
> miniparrot...................................skipped.
> Loading platform and local hints
> files................................done.
> Determining nongenerated header
> files.................................done.
> Determining what C compiler and linker to
> use.........................done.
Is this the test which you say "apparently passed"?
> Determining whether make is
> installed..................................yes.
> Determining whether lex is
> installed...............................skipped.
> Determining whether yacc is
> installed..............................skipped.
> Determining if your C compiler is actually gcc...
> step auto::gcc died during execution: C compiler failed (see test.cco)
> at lib/Pa
> rrot/Configure/Step.pm line 504
> Parrot::Configure::Step::cc_build() called at
> config/auto/gcc.pm line 37
>
> auto::gcc::runstep('auto::gcc=HASH(0x1e1db18)',
> 'Parrot::Configure=HASH(
> 0x1a52550)') called at lib/Parrot/Configure.pm line 267
> eval {...} called at lib/Parrot/Configure.pm line 261
> Parrot::Configure::_runstep('Parrot::Configure=HASH(0x1a52550)',
> 'Parrot
> ::Configure::Task=HASH(0x1a52ab4)', 'undef', 'undef', 'undef', 11)
> called at lib
> /Parrot/Configure.pm line 192
> Parrot::Configure::runsteps('Parrot::Configure=HASH(0x1a52550)')
> called
> at Configure.pl line 324
>
> at Configure.pl line 324
[snip]
kid51
