Anyone out there using the Intel compiler?
How are you running Configure.pl?
Thanks,
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Andy Lester wrote:
The long-term plan for the headerizer is that it will take all the
prototypes for all the functions and populate all the .h files
automatically. No need to worry about differences between header and
source, because the header comes from it. It'll also auto-generate
attribu
On Wed Jun 06 00:45:25 2007, ptc wrote:
> On Mon Feb 20 14:35:58 2006, jhoblitt wrote:
> > > [jhoblitt at hawaii.edu - Wed Dec 14 01:56:56 2005]:
> > >
> > > - The framework itself needs tests!!!
> > >
> > > Parrot::Configure::Data should be low hanging fruit
> >
> > This has been mustly done s
The long-term plan for the headerizer is that it will take all the
prototypes for all the functions and populate all the .h files
automatically. No need to worry about differences between header and
source, because the header comes from it. It'll also auto-generate
attributes for each of
On 5/20/07, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
I sent this message a few days ago, but hasn't reached the list I think:
hi,
I experimented on windows with removing some libs that seemed unnecessary,
and I ended with this line in my Makefile;
C_LIBS = kernel32.lib ws2_32.lib msvcrt
Paul Cochrane wrote:
>> Without the manual setting of PATH before building?
>
> With the manual PATH setting. There are several tickets for cygwin
> not building in RT; are they all related? Is there something like a
> hints file where the information about the PATH can be set so that
> cygwin b
Joshua Gatcomb writes:
: I build parrot on Cygwin circa 5x a week. Anytime it fails to build, I
: perform the following:
:
: 1. make realclean
: 2. svn up
: 3. perl Configure.pl
: 4. PATH=/home/me/parrot/blib/lib:/bin
: 5. make
Joy! Looks like t/stm/queue is wedged.
Thanks,
Greg
Paul Cochrane writes:
> as you can see in the snippets above from the weekly rt summary
> message, we have 500+ tickets. many of these are unclassified with
> regard to platform, severity, language, etc. classification of these
> tickets, and creation of shared queries we can use to manage the
All:
I build parrot on Cygwin circa 5x a week. Anytime it fails to build, I
perform the following:
1. make realclean
2. svn up
3. perl Configure.pl
4. PATH=/home/me/parrot/blib/lib:/bin
5. make
In the very few instances it still fails, I isolate the build that it
started failing and report
> as you can see in the snippets above from the weekly rt summary
> message, we have 500+ tickets. many of these are unclassified with
> regard to platform, severity, language, etc. classification of these
> tickets, and creation of shared queries we can use to manage the queue
> will make it easi
On Mon Feb 20 14:35:58 2006, jhoblitt wrote:
> > [jhoblitt at hawaii.edu - Wed Dec 14 01:56:56 2005]:
> >
> > - The framework itself needs tests!!!
> >
> > Parrot::Configure::Data should be low hanging fruit
>
> This has been mustly done since Decemeber with the expection of
> Parrot::Configure
Without the manual setting of PATH before building?
With the manual PATH setting. There are several tickets for cygwin
not building in RT; are they all related? Is there something like a
hints file where the information about the PATH can be set so that
cygwin builds out of the box?
Paul
12 matches
Mail list logo
