Date: Fri, 05 Jan 2007 08:46:27 +0800 From: "Steven D. Yee" <sdy@email.com> To: "David Landgren" <david@landgren.net> Cc: freebsd-questions@freebsd.org Subject: Re: sparc64 and perl 5.8.8 port test failures? Message-ID: <20070105004628.170E3872DC@cal1-1.us4.outblaze.com>
next in thread | raw e-mail | index | archive | help
I tried deleting the work subdirectory and doing both a 'make' and 'make WITHOUT_PERL_64BITINT=3Dyes' 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 con= fusing 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 fig= ure out why the port just doesn't work as is. steve. > ----- Original Message ----- > From: "David Landgren" <david@landgren.net> > To: "Steven D. Yee" <sdy@email.com> > Subject: Re: sparc64 and perl 5.8.8 port test failures? > Date: Wed, 03 Jan 2007 08:49:49 +0100 >=20 >=20 > 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. >=20 > [...] >=20 > > ../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=3Dyes 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=20 > > (even use64bitint is defined) > > > > does anyone have any pointers as to what may be going on? or=20 > > where to start looking? >=20 > This looks like the build is bringing in 64bitness when it=20 > shouldn't (or vice versa). The build process might have remnants of=20 > the previous config run lying around (in Policy.sh and/or=20 > config.sh). Step down into the build directory and delete these two=20 > files, and build again. >=20 > Or, better yet, just delete the entire ./work directory, and build it aga= in. >=20 > Later, > DAvid > --=20 ___________________________________________________ Search for products and services at: http://search.mail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070105004628.170E3872DC>