Will Coleda wrote:

>  
>  On Dec 10, 2006, at 10:51 AM, James Keenan wrote:
>  
> >
> > On Dec 10, 2006, at 10:04 AM, Will Coleda via RT wrote:
> >
> >>
> >> On Dec 9, 2006, at 10:26 PM, James Keenan (via RT) wrote:
> >>
> >>> # New Ticket Created by  James Keenan
> >>> # Please include the string:  [perl #41064]
> >>> # in the subject line of all future correspondence about this issue.
> >>> # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=41064 >
> >>>
> >>>
> >>> Once again I am unable to successfully 'make' Parrot on Darwin.  I
> >>> getting the same errors I was getting when I first tried at the
> >>> Chicago hackathon on Nov 11 -- nothwithstanding (a) having succeeded
> >>> with 'make' since then several times; and (b) applying all the hack
> >>> workarounds suggested at the hackathon.
> >>
> >>
> >> <SNIP>
> >>
> >>> 60,95d58
> >>> < ops2c.pl: Cannot open source file 'src/ops/core_ops_cgp.c.temp'
> >>> for writing: Permission denied!
> >>
> >>
> >> AOOGA.
> >>
> >>> < make: *** [src/ops/core_ops_cgp.c] Error 13
> >>> < [parrot] 523 $ ls -l src/ops/core_ops_cgp.c.temp
> >>> < -rw-r--r--   1 root  jimk  0 Dec  7 20:59 src/ops/
> >>> core_ops_cgp.c.temp
> >>> < [parrot] 524 $ ls -l src/ops/
> >>> < total 3536
> >>> < -rw-r--r--   1 jimk  jimk    7046 Nov 12 08:08 bit.ops
> >>> < -rw-r--r--   1 jimk  jimk   22308 Nov 12 08:08 cmp.ops
> >>> < -rw-r--r--   1 jimk  jimk   28238 Nov 12 08:08 core.ops
> >>> < -rw-r--r--   1 jimk  jimk  838227 Dec  9 21:32 core_ops.c
> >>> < -rw-r--r--   1 jimk  jimk  317139 Dec  9 21:32 core_ops_cg.c
> >>> < -rw-r--r--   1 root  jimk       0 Dec  7 20:59 core_ops_cgp.c.temp
> >>
> >>
> >> Looks like you ran 'make' as root at one point, and are now running
> >> it as jimk. The temp file that was left out there is owned by root,
> >> not deletable by your normal account. This would explain why things
> >> seem to fail only on your box.
> >>
> >
> > I'm not sure how that temp file owned by root got there, but I  
> > deleted it, did make realclean and attempted to remake.  But I  failed 
> > again, as documented in the second of 3 attachments  submitted yesterday.
>  
>  
>  Ok. Few questions:
>  
>  What arguments did you pass to configure?

As mentioned in OP, I made two attempts.   The first was to call perl 
Configure.pl with no arguments.  The second:

perl Configure.pl --without-gmp --cc=gcc --ccflags=-DAN
# options suggested as workarounds at hackathon
# -DAN was suggested by Chip as a dummy option to get around some problem

>  What version of the compiler are you using?

gcc 3.81:  the latest
Parrot:  svn 16056 (see myconfig attached)

>  What chip architecture (you said darwin, I'm assuming OS X here: if  so, 
>  what does sw_vers say?)

[parrot] 624 $ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.4.8
BuildVersion:   8L127

... plus see perl_V attached

>  Have you ever installed parrot before?
>  
'make install'?  No, but I was told that developers probably shouldn't 
go that far.  My first exposure to Parrot was at the Chicago Perl 
hackathon, where I experience problems very similar to those I'm 
reporting in this thread.  Chip, chromatic, particle and others 
suggested workarounds (described in previous threads) which got me to 
the point where I could start writing tests of the build tools.  I went 
through the make realclean/Configure.pl/make cycle quite a few times 
over the past month, succeeding to the point where I've been able to run 
'make test' and file reports on failing tests.

But in the last couple of days I cannot 'make' successfully, as reported 
earlier in this thread.

kid51