Re: sparc64 and perl 5.8.8 port test failures?
I tried deleting the work subdirectory and doing both a 'make' and 'make WITHOUT_PERL_64BITINT=yes' but make test still fails the same way on both the pack and integer tests .. is it possible that there is some misconfiguration in my system that is confusing the configure script w.r.t. 64bitness of my machine ? I guess I could start mucking with the config.sh by hand but I'd rather figure out why the port just doesn't work as is. steve. > - Original Message - > From: "David Landgren" <[EMAIL PROTECTED]> > To: "Steven D. Yee" <[EMAIL PROTECTED]> > Subject: Re: sparc64 and perl 5.8.8 port test failures? > Date: Wed, 03 Jan 2007 08:49:49 +0100 > > > Steven D. Yee wrote: > > I'm seeing multiple errors from make test and I can't seem to > > figure out how to get rid of them. As far as I can > > tell it builds correctly. > > [...] > > > ../lib/integer..NOK 10 > > # Failed test 'left shift' > > # in ../lib/integer.t at line 49. > > # got: '-4292583424' > > # expected: '-9223372036854775808' > > # Looks like you failed 1 test of 11. > > ../lib/integer..dubious > > Test returned status 1 (wstat 256, 0x100) > > DIED. FAILED test 10 > > Failed 1/11 tests, 90.91% okay > > > > > > I did try building with WITHOUT_PERL_64BITINT=yes but that didn't > > seem to make a difference, although its possible that I screwed that > > up since conf.sh still shows multiple references to 64 bit ints > > (even use64bitint is defined) > > > > does anyone have any pointers as to what may be going on? or > > where to start looking? > > This looks like the build is bringing in 64bitness when it > shouldn't (or vice versa). The build process might have remnants of > the previous config run lying around (in Policy.sh and/or > config.sh). Step down into the build directory and delete these two > files, and build again. > > Or, better yet, just delete the entire ./work directory, and build it again. > > Later, > DAvid > -- ___ Search for products and services at: http://search.mail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sparc64 and perl 5.8.8 port test failures?
Steven D. Yee wrote: I'm seeing multiple errors from make test and I can't seem to figure out how to get rid of them. As far as I can tell it builds correctly. [...] ../lib/integer..NOK 10 # Failed test 'left shift' # in ../lib/integer.t at line 49. # got: '-4292583424' # expected: '-9223372036854775808' # Looks like you failed 1 test of 11. ../lib/integer..dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 10 Failed 1/11 tests, 90.91% okay I did try building with WITHOUT_PERL_64BITINT=yes but that didn't seem to make a difference, although its possible that I screwed that up since conf.sh still shows multiple references to 64 bit ints (even use64bitint is defined) does anyone have any pointers as to what may be going on? or where to start looking? This looks like the build is bringing in 64bitness when it shouldn't (or vice versa). The build process might have remnants of the previous config run lying around (in Policy.sh and/or config.sh). Step down into the build directory and delete these two files, and build again. Or, better yet, just delete the entire ./work directory, and build it again. Later, DAvid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sparc64 and perl 5.8.8 port test failures?
Steven D. Yee wrote: I'm seeing multiple errors from make test and I can't seem to figure out how to get rid of them. As far as I can tell it builds correctly. [...] ../lib/integer..NOK 10 # Failed test 'left shift' # in ../lib/integer.t at line 49. # got: '-4292583424' # expected: '-9223372036854775808' # Looks like you failed 1 test of 11. ../lib/integer..dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 10 Failed 1/11 tests, 90.91% okay I did try building with WITHOUT_PERL_64BITINT=yes but that didn't seem to make a difference, although its possible that I screwed that up since conf.sh still shows multiple references to 64 bit ints (even use64bitint is defined) does anyone have any pointers as to what may be going on? or where to start looking? This looks like the build is bringing in 64bitness when it shouldn't (or vice versa). The build process might have remnants of the previous config run lying around (in Policy.sh and/or config.sh). Step down into the build directory and delete these two files, and build again. Or, better yet, just delete the entire ./work directory, and build it again. Later, DAvid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"