From: "Patrick R. Michaud" <[EMAIL PROTECTED]>
Date: Fri, 29 Jun 2007 13:42:18 -0500
On Fri, Jun 29, 2007 at 05:59:38PM +0100, Nicholas Clark wrote:
> > >>>Modified since when?
>
> Since the last time the user ran Configure.
> (For the default test run)
>
> I think tha
I noticed the failure 6/29 at r19501. Binary search of trunk indicates that
r19489 passed
'make', but 19495 failed.
kid51
Patrick R. Michaud wrote:
This presumes that every PMC class also has a Namespace PMC associated with it
that points to the class. I'm not sure that's true for Parrot PMC classes.
It's what I've implemented, though whether it's The Design is another
question that I'm not clear on the answer
Parrot fails with an optimized build on Win32, Visual C++. Here are a
few random observations, not sure if they are pointing to the problem or
are merely side effects.
It seems like the failures only affect JIT execution. I'm only seeing
this with some shootout tests during C, as those are setti
perl Configure.pl --cc=icc --link=icc --ld=icc
--ccflags=-I/opt/intel/compiler91/include/
Even with this, I get complaints that:
icc: error #10001: could not find directory in which the set of
libstdc++ include files resides
I've apparently got a libstdc++-devel package installed at /usr
pancake wrote:
> (...)
> Ok, after the presentations.. I have some problems for writing the patches
> because more than one bug report matches the same source file, and i have to
> wait everytime for commits before doing anything more. I understand that this
> is my problem and I should be pacient,
On 07/06/07, Paul Cochrane <[EMAIL PROTECTED]> wrote:
> perl Configure.pl --cc=icc --link=icc --ld=icc
I tried this, but got the following output from Configure.pl:
[EMAIL PROTECTED] parrot_svn2 $ perl Configure.pl --cc=icc --link=icc --ld=icc
Parrot Version 0.4.12 Configure 2.0
Copyright (C) 2
