X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f NNTP-Posting-Date: Thu, 17 Apr 2008 19:37:15 -0500 From: "Robbie Hatley" Newsgroups: comp.lang.perl.misc,comp.os.msdos.djgpp References: Subject: Re: Perldoc error: "Could not create temp file" Date: Thu, 17 Apr 2008 17:37:05 -0700 Organization: Tustin Free Zone X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1914 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 Message-ID: Lines: 76 X-Usenet-Provider: http://www.giganews.com X-Trace: sv3-ZYqlRw6tJJFaANKAmG4zjZSXnEhm/vCRCq/WgEbGNNWkfF3e1YzMyq7QgNfmxgulZzWzif03BMEax28!wJw40iO68o5tcswVQTINjbiicwEeUEXKcT7gB2qYNQRMYsgBNLoTn6/1rlgONP73eqS+8E5agA== X-Complaints-To: abuse AT giganews DOT com X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.39 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "A. Sinan Unur" wrote: > Here is my guess, File::Temp is OK, but Pod::Perldoc only seems to > check and take care of the shortcomings of Win32. However, the same > shortcomings exist in DJGPP running on Win32 as well. I did look at > MSWin_perldoc_tempfile in Perldoc.pm and it looks like the DJGPP > would need special handling as well. > > The only Win32 specific part of the special handling seems to be > getting the tick count for generating a unique filename. > > I don't have a DJGPP environment set up right now so I can't test a > patch, but, if you don't care much about filenames being > unguessable, replacing the filename generation algorithm to > something along the lines of > > sub DJGPP_perldoc_tempfile { > > # skip, see sub MSWin_perldoc_tempfile > > # completely untested > > my $ext = 'aaa'; > > do { > > # used also in MSWin_temp_cleanup > > $spec = catfile( > $tempdir, > sprintf( 'pd%6.6x.%s', time & 0x00ffffff, $ext ), > ); > ++ $ext; > } while ( -e $spec ); I'll try that, but i'm not hopeful. The error messages show different random 10-character file names each time I try running Perldoc. So perldoc.pm is successfully coming up with random file names, but they apparently get rejected somewhere. Hmmm... 10 characters... I wonder if something in the DJGPP version of Perl or perldoc.pm is expecting 8x3 DOS file names? If so, it may reject 10x3. How would I go about altering perldoc.pm to use 8x3 instead of 10x3 temp file names? > Alternatively, you can try UNLINK => 0 and see if it solves you > immediate problem. I think that's one of the things I tried last night, but I'll make sure after work tonight. I'm curious: Have any of the others in these two groups had problems running perldoc on DJGPP on Win2K? Or more to the point, can anyone here SUCCESSFULLY run DJGPP perldoc on Win2K? I'm wondering if this is a widespread bug, or just some fluke of setup of the 2 machines I'm seeing it on. I know that djgpp perldoc USED to work on Win2k. But after a hard-disk crash a few months ago, I recreated my djgpp folder with all the lastest stuff, almost certainly newer versions; so I'm suspecting this may be a bug in the 5.8.8 version of djgpp Perl. Is anyone here running DJGPP and Perl 5.8.8 on Win2K? If so, please try this: Run Bash, then at Bash prompt type "perldoc perl". Do you get "invalid argument in perldoc.pm line 1483"? Or does it work fine? -- Cheers, Robbie Hatley lonewolf aatt well dott com www dott well dott com slant user slant lonewolf slant