Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Locale-Maketext-Lexicon CPAN distribution.

Report information
The Basics
Id: 14688
Status: resolved
Priority: 0/
Queue: Locale-Maketext-Lexicon

People
Owner: Nobody in particular
Requestors: steve.hay [...] uk.radan.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.49
Fixed in: (no value)



Subject: xgettext suffers from perl bug #37223
I'm running perl-5.8.7 on Windows XP. xgettext doesn't work on Win32 because it uses "follow => 1" in its File::Find::find() call, which dies on Win32 -- see perl bug #37223. For example, if, in C:\Temp, I create a directory called "dir" containing an empty file called "file" and an empty sub-directory called "subdir" and then run the command: xgettext -D dir file then I get the error: C:/Temp/dir/subdir encountered a second time at C:/perl5/lib/File/Find.pm line 560. In order to function properly with existing perls that have this broken File::Find behaviour, xgettext should either not use "follow => 1" (at least, not on Win32), or should at least provide a command-line option for disabling the "follow symlink" behaviour that Win32 users could make use of.
On Wed Sep 21 10:58:52 2005, SHAY wrote: Show quoted text
> I'm running perl-5.8.7 on Windows XP. > > xgettext doesn't work on Win32 because it uses "follow => 1" in its > File::Find::find() call, which dies on Win32 -- see perl bug > #37223. > > For example, if, in C:\Temp, I create a directory called "dir" > containing an empty file called "file" and an empty sub-directory > called "subdir" > > and then run the command: > > xgettext -D dir file > > then I get the error: > > C:/Temp/dir/subdir encountered a second time at > C:/perl5/lib/File/Find.pm line 560. > > In order to function properly with existing perls that have this > broken File::Find behaviour, xgettext should either not use "follow > => 1" (at least, not on Win32), or should at least provide a > command-line option for disabling the "follow symlink" behaviour > that Win32 users could make use of.
Hiya I'm closing this bug as it was fixed in 0.52. regards Clint