Hi,
James Keenan via RT schreef:
According to our records, your request regarding
"[BUG] compiler detection failure"
has been resolved.
If you have any further questions or concerns, please respond to this message.
For other topics, please create a new ticket.
<URL: http://rt.perl.org/rt3/Ticket/Display.html?id=51340 >
I see. Well, it's a matter of how you view things, isn't it? You could
see the history of this report as someone doing his utmost to correspond
about a problem he doesn't see himself. Or you could see it as the
report having been handled by someone who didn't have the matching
hardware and asked for information that was already in the message.
I have no idea whether I saw his message at the time, nor what kind of
reply I sent if I did see it. But I downloaded parrot-0.9.0 to test, and
when after untarring I perl Configure.pl, I get the following result:
----- Start of include: -----
Parrot Version 0.9.0 Configure 2.0
Copyright (C) 2001-2008, The Perl Foundation.
Hello, I'm Configure. My job is to poke and prod your system to figure out
how to build Parrot. The process is completely automated, unless you
passed in
the `--ask' flag on the command line, in which case I'll prompt you for
a few
pieces of info.
Since you're running this program, you obviously have Perl 5--I'll be
pulling
some defaults from its configuration.
init::manifest - Check
MANIFEST.....................................done.
init::defaults - Set Configure's default
values.....................done.
init::install - Set up installation
paths..........................done.
init::hints - Load platform and local hints
files................done.
init::headers - Find header files distributed with
Parrot..........done.
inter::progs - Determine what C compiler and linker to
use...Compilation failed with 'cc'
----- End of include. -----
And, yes, that means it failed at that time. And no, I do not have more
output about other failures, for if I had had more output it would be
there: This is not part of the result, it's all of it. The only thing I
left out is that my shell will once again print a command prompt once
this has finished.
I haven't checked whether the documentation still speaks about a
myconfig, but in any case, I don't see it being created. Lacking such
feedback, I instead return to you the revealing results of using
perl Configure.pl --verbose-step=inter::progs
----- Start of include: -----
Parrot Version 0.9.0 Configure 2.0
Copyright (C) 2001-2008, The Perl Foundation.
Hello, I'm Configure. My job is to poke and prod your system to figure out
how to build Parrot. The process is completely automated, unless you
passed in
the `--ask' flag on the command line, in which case I'll prompt you for
a few
pieces of info.
Since you're running this program, you obviously have Perl 5--I'll be
pulling
some defaults from its configuration.
init::manifest - Check
MANIFEST.....................................done.
init::defaults - Set Configure's default
values.....................done.
init::install - Set up installation
paths..........................done.
init::hints - Load platform and local hints
files................done.
init::headers - Find header files distributed with
Parrot..........done.
inter::progs - Determine what C compiler and linker to use...
ccflags: -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBIAN
-pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
cc -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBIAN -pipe
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I./include -c test_7926.c
cc -L/usr/local/lib -Wl,-E test_7926.o -o test_7926 -ldl -lm
-lpthread -lcrypt
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld gaf exit-status 1 terug
Compilation failed with 'cc'
----- End of include. -----
Same notes as before.
I hope it's of any help.
BFN
--
Peter Hans van den Muijzenberg
Sneek
p...@home.nl
