Gerd Pokorra wrote:
The configuration for Parrot don't work on the PowerPC architectur and
Fedora linux. I attached a log of the build. In the build I include
the command "perl Configure.pl --test". For my surprice all tests passes
successful but the configuration fails. Is the ppc-CPU-architectur a
platform where Parrot should run and should I open a ticket for that?
[snip]
> tools/dev/install_files.pl tools/dev/mk_manifests.pl
> Can't open tools/dev/mk_manifests.pl: No such file or directory, <>
line 277.
> + exit 0
I'm not sure what you were aiming for here. For two years (at least),
we have had no file called: mk_manifests.pl.
Perhaps you were thinking of: tools/dev/mk_manifest_and_skip.pl ?
> /usr/bin/perl Configure.pl --test
This configured. Did you attempt to build parrot with this?
[snip]
> + /usr/bin/perl Configure.pl --prefix=/usr --libdir=/usr/lib
> --sysconfdir=/etc --infodir=/usr/share/info --mandir=/usr/share/man
> --cc=gcc --cxx=g++ '--optimize=-O2 -g -pipe
> -Wall -Wp,-D_FORTIFY_SOURCE=2
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32
> -maccumulate-outgoing-args' --parrot_is_shared --lex=/usr/bin/flex
> --yacc=/usr/bin/yacc '--libs=-lcurses -lm'
At the very least, I congratulate you for trying this configuration. In
the two-and-a-half years I've been involved with Parrot, I have never
seen a report of configuration with so many attempted command-line options.
That being said, the only way I think we could debug this would be to
try configuring with fewer of these options and see whether
configuration fails when we add options one at a time.
[snip]
> auto::alignptrs - Determine your minimum pointer alignment...
> step auto::alignptrs died during execution: C compiler failed (see
test_15591.cco) at lib/Parrot/Configure/Compiler.pm line 104
>
Parrot::Configure::Compiler::cc_build('Parrot::Configure=HASH(0x10208360)')
called at config/auto/alignptrs.pm line 51
> auto::alignptrs::runstep('auto::alignptrs=HASH(0x1054ea98)',
'Parrot::Configure=HASH(0x10208360)') called at lib/Parrot/Configure.pm
line 412
> eval {...} called at lib/Parrot/Configure.pm line 412
>
Parrot::Configure::_run_this_step('Parrot::Configure=HASH(0x10208360)',
'HASH(0x1044dba8)') called at lib/Parrot/Configure.pm line 267
> Parrot::Configure::runsteps('Parrot::Configure=HASH(0x10208360)')
called at Configure.pl line 75
> at Configure.pl line 75
The Parrot configuration steps are cumulative. Later steps often depend
on data recorded inside the Parrot::Configure object during earlier
steps. So I would recommend cutting back the command-line options until
you can at least get past auto::alignptrs.
Does anyone else see interactions among the command-line options which
might cause configuration to fail?
Thanks for your report.
kid51
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
