Vladimir Lipskiy:
> Is there anybody who could drop a couple of lines on account of this
> question while
> Brent is unget-at-able?
Not quite un-get-at-able--just unable-to-hack-able. :^)
> > Hey, I use win32 (mingw) and the JIT has always worked fine for me. If
> this
> > is an issue with MSVC,
> >> if (-e "jit/$cpuarch/core.jit" and $osname ne 'MSWin32') {
Yeah, you're right. Thanks.
Index: jit.pl
===
RCS file: /cvs/public/parrot/config/auto/jit.pl,v
retrieving revision 1.18
diff -r1.18 jit.pl
71c71
< if (-e "jit/$cpuarch
> > > There *is* code in config/auto/jit.pl to disable JIT on Win32, so I'm
not
> > > sure why Parrot's trying to compile it. I *do* know that it was
working
> > > fine before the exec stuff went in--perhaps looking at the diffs on
jit.pl
> > > will be enlightening. Unfortunately, I'm away from m
"Vladimir Lipskiy" <[EMAIL PROTECTED]> writes:
>> if (-e "jit/$cpuarch/core.jit" and not $osname == 'MSWin32'){
ITYM:
>> if (-e "jit/$cpuarch/core.jit" and $osname ne 'MSWin32') {
--
Lars Balker Rasmussen Consult::Perl
--- Vladimir Lipskiy <[EMAIL PROTECTED]> wrote:
> > Jonathan Worthington:
> > > LIB : fatal error LNK1181: cannot open input file "jit_cpu.obj"
> > > NMAKE : fatal error U1077: 'lib' : return code '0x49d'
> > > Stop.
>
> >
> > There *is* code in config/auto/jit.pl to disable JIT on Win32, so I'm n
> Jonathan Worthington:
> > LIB : fatal error LNK1181: cannot open input file "jit_cpu.obj"
> > NMAKE : fatal error U1077: 'lib' : return code '0x49d'
> > Stop.
>
> There *is* code in config/auto/jit.pl to disable JIT on Win32, so I'm not
> sure why Parrot's trying to compile it. I *do* know that
Jonathan Worthington:
> LIB : fatal error LNK1181: cannot open input file "jit_cpu.obj"
> NMAKE : fatal error U1077: 'lib' : return code '0x49d'
> Stop.
This is unrelated to the warning in spf_render.c.
I apologize--I spotted this bug just before I went on vacation, and forgot
to report it. Conf
