Re: OS X tests

2005-02-03 Thread Matt Diephouse
William Coleda <[EMAIL PROTECTED]> wrote: > Just did a fresh checkout and now I no longer get test failures on OS X. (not > specifying a -prefix) Alright, I just did the same (but used a --prefix) and all tests passed here as well. And this right after I sent my "me too" message (I didn't see thi

Re: OS X tests (was: Building with VS.NET 2003 and ICU 2.8 on Win32)

2005-02-03 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Will Coleda wrote: > > I don't know if this is related to my build problems on OS X which have > > gone warnocked. Trying to build without specifying a --prefix to > > Configure causes all the dynclasses to fail > > I can't reproduce that here - it test

Re: [perl #33171] Error When Reading Past EOF

2005-02-03 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse <[EMAIL PROTECTED]> wrote: > > > That still results in "in file (unknown) near line -1" being printed > > as part of the error message, so I'm leaving this ticket open. (It > > annoys me.) > > *g* > > I've changed now the policy for inc

Re: OS X tests

2005-02-03 Thread William Coleda
Just did a fresh checkout and now I no longer get test failures on OS X. (not specifying a -prefix) Leopold Toetsch wrote: Will Coleda wrote: I don't know if this is related to my build problems on OS X which have gone warnocked. Trying to build without specifying a --prefix to Configure causes

[perl #34039] Build failure on freebsd 4.9-RELEASE (mpz_*)

2005-02-03 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #34039] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=34039 > bash-2.05b$ gmake Compiling with: xx.c cc -DAPPLLIB_EXP=/usr/local/lib/perl5/5.6.1/BSDPA

[perl #24168] gmake required to build imcc on freebsd

2005-02-03 Thread Will Coleda via RT
This is still the case. Documented in PLATFORMS, closing ticket. > [psinno - Thu Oct 09 02:45:59 2003]: > > Hi, >currently gmake seems to be required to build imcc on freebsd.

[perl #18003] Make test failures under Win32 MSVC++

2005-02-03 Thread Ron Blaschke via RT
> Failed Test Status Wstat Total Fail Failed List of Failed > > > t/src/basic.t255 65280 22 100.00% 1-2 > t/src/intlist.t 255 65280 44 100.00% 1-4 > t/src/list.t 255 65280 11 1

[perl #23552] Parrot on Win32! Where we will be able to compile IMCC?!

2005-02-03 Thread Ron Blaschke via RT
IMCC seems to run fine, or am I missing the point? Unless someone objects I'd say we close this one. >nmake test_imcc Microsoft (R) Program Maintenance Utility Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. C:\Perl\bin\perl.exe t\harness imcc\t\*\*.t imcc\t\

Re: [Repost] Building with VS.NET 2003 and ICU 2.8 on Win32

2005-02-03 Thread Ron Blaschke
Sriram Krishnan wrote: > Thanks for the reply. Readme.Win32 should have a notice about building in > anything other than Visual Studio 6. Since 'msdev' is hardcoded inside the > ICU build stuff, it *won't build on anything other than Visual Studio 6*. > For anyone interested, I've written step-by-s

Re: [Repost] Building with VS.NET 2003 and ICU 2.8 on Win32

2005-02-03 Thread Ron Blaschke
Jonathan Worthington wrote: > "Ron Blaschke" <[EMAIL PROTECTED]> wrote: >> Leopold Toetsch wrote: >>> Sriram Krishnan <[EMAIL PROTECTED]> wrote: >> Failed TestStat Wstat Total Fail Failed List of Failed >> --

Re: Parrot_load_bytecode

2005-02-03 Thread Leopold Toetsch
Ian Joyce <[EMAIL PROTECTED]> wrote: > Is there a way to determine if Parrot_load_bytecode fails to load > and/or compile an imc file? I am assuming no because > Parrot_load_bytecode has a type of void. Yep. If something goes wrong it calls internal_exception. That'll be a catchable real_exception

Re: [perl #34029] [PATCH][MSWin32] Get nci test to link again

2005-02-03 Thread Leopold Toetsch
Ron Blaschke <[EMAIL PROTECTED]> wrote: > Attached patch will get libnci_test to link on Win32. Thanks, applied. leo

Re: [perl #33171] Error When Reading Past EOF

2005-02-03 Thread Leopold Toetsch
Matt Diephouse <[EMAIL PROTECTED]> wrote: > That still results in "in file (unknown) near line -1" being printed > as part of the error message, so I'm leaving this ticket open. (It > annoys me.) *g* I've changed now the policy for including source line information. Unless -O is given file and l