RE: [coLinux-users] Gentoo (Deluxe) - Perl compile issues?

[Michael L. <mi...@s2...>]

Well, I'm using NTFS, so perhaps we can rule that out...  :) 

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of David
Kaufman
Sent: May 31, 2004 12:19 PM
To: col...@li...
Cc: col...@li...; Dan Aloni
Subject: Re: [coLinux-users] Gentoo (Deluxe) - Perl compile issues?

> Michael Laccetti wrote:
>>> Not sure if anybody else is having this problem, or I'm just the 
>>> lucky soul.  ...using Gentoo ... 'emerge sync' followed by 'emerge 
>>> -u world'.  The world upgrade chokes horribly on upgrading Perl, for 
>>> some reason.  Has anybody seen this problem, and better yet, 
>>> resolved it?  I'm having a specific problem with the tests that are 
>>> performed, it basically hangs at the following 
>>> 'lib/Benchmark........................'
>>>
>> Joel Moore wrote
>>
>> I have the same problem.  I didn't notice it eating CPU, I thought it 
>> was just hung and doing nothing, but I could be wrong.
>>
>
> Well, I've done an emerge inject perl-5.8.4 just to get past it.  But 
> still, this is a bit of a showstopper.  If you can't emerge -u world, 
> that's not a good sign.

it's not limited to gentoo either, of course.

the make tests also fail for Time::Hires, and thus for all the Benchmarks,
even when compiling perl 5.8.4 on the coLinux-supplied debian filesystem
image.  i was trying this perlmonks tutorial "Install parallel Perl on
Debian" [ http://perlmonks.thepen.com/285799.html ]

i think it has something to do with the fact that my underlying filesystem
is FAT32 instead of NTFS.  FAT32 files have a time "resolution" of just less
that 2 seconds, which confuses compilers and makes Time::Hires think it has
failed when it hasn't really -- the filesystem has failed it.

the only workaround i know of is to just not run "make test" when compiling
perl -- not an optimal solution, of course.  but i skipped it and just did a
make install and my new perl 5.8.4 installed flawlessly and works great.

i'd be interested to see if it really *is* the FAT32 -second time resolution
limitation that is causing this, and if so, what can be done about it to
make perl detect the environment, and skip the test on this platform, as
perl for windows does on FAT32 volumes.  are you two both running colinux on
Fat32-formatted drives?  if you're not sure then, in explorer, right-click
the drive colinux is installed on, select properties, and "General" tab
should show

       Type: Local Disk
File System: FAT32

if it says NTFS instead of FAT32 and you're getting this error compiling
perl, then drop me a note so i can look into it further.

Dan, if my suspicions are right, how could perl tests running on coLinux
even *discover* that the host filesystem is FAT32 so that we can teach them
to skip these tests?  and wouldn't there have to be some run-time test perl
could do to learn the host filesystem, since the colinux image might be
moved to and from different filesystems while it was "asleeep"?

-dave



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest
thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users