From: Juan Manuel Guerrero on
OFYI:
The error reported can not be reproduced by me on the
systems that are available to me.

The perl 5.8.8 port works flawlessly on the following
operating systems:
1) MSDOS 6.22 (SFN)
2) Win98SE (SFN)
3) Win98SE (LFN)
4) WinXP (home) SP2 (LFN)

It fails and will continue to failing in the future
because I have no intentions to fix it:
1) WinXP (home) SP2 (SFN)

The reason for this failure is that AFAIK there is
no way to inhibit the generation of numeric tails
for short file names. This means that a long file
name like this:
longfilename.extension
has a short file name alias that looks like this:
longfi~1.ext
and this will not be found by perl or any other djgpp
program. On Win98 there is always the possibility to
disable the numeric tail generation so that:
longfilename.extension
is cleanly truncated to 8.3 and becomes:
longfile.ext
The OS will truncated in this way the long file name
passed by the application (perl) and looks for the file
with the truncated name and will find it.
If the long file name is not truncated in this way to the
8.3 length but changed by the OS like this
longfi~1.ext
the application will never find the file.
To be able to run djgpp applications with an OS that
generates numeric tails for the SFN aliases almost the
complete stdio of the application must be replaced and
I have not the time to do that.
IMHO there is no reason to use SFN where LFN support is
available.
In conclusion; *no one* of the ports I have produced is
able to run in SFN environments that use numeric tails.
I have never added djgpp specific code that is able to
handle SFN with numeric tails and that is started if
the file can not be found using the long file name.


Anyway all this does not explain the failure that has been
reported. On my WinXP box I have set LFN=n in djgpp.env
and started bash. I started the command:
perldoc perl
and got the following output:


perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LC_ALL = (unset),
LANG = "de"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Can't locate File/Spec/Functions.pm in @INC (@INC contains: /dev/env/
DJDIR/lib/perl5 /dev/env/DJDIR/lib/perl5/site /dev/env/DJDIR/lib/perl5/
site /dev/env/DJDIR/lib/perl5/site .) at /dev/env/DJDIR/lib/perl5/Pod/
Perldoc.pm line 10.
BEGIN failed--compilation aborted at /dev/env/DJDIR/lib/perl5/Pod/
Perldoc.pm line 10.
Compilation failed in require at c:/djgpp/bin/perldoc line 9.
BEGIN failed--compilation aborted at c:/djgpp/bin/perldoc line 9.


The application fails before it reaches the point where the
temporary file is created. The applications is not even
capable to start because it can not load the required
modules. This is due the numeric tails in the file and
directory names.

Regards,
Juan M. Guerrero
From: Robbie Hatley on

Juan Manuel Guerrero wrote:

> Robbie Hatley schrieb:
> [snip]
> > 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.
>
> Perl 5.8.8 compiled with djdev203 runs flawlessly on my Win98SE box
> and perl 5.8.8 compiled with djdev204 runs flawlessly on my
> WinXP box too. I can not reproduce the error you are reporting in
> any way.

Win98SE and WinXP are not Win2K.

> No, it always works on all OS I have tried on different computers.

On all OSs except Win2K, apparently.

Is anyone here running djgpp Perl 5.8.8 on Microsoft Windows 2000
Professional? If so, does perldoc work for you? If you launch Bash
and type "perldoc perl<CR>", do you get an error message saying:

Error in tempfile() using c:/djgpp/tmp/XXXXXXXXXX:
Could not create temp file c:/djgpp/tmp/zkQ06tqlcH:
Invalid argument (EINVAL) at
/dev/env/DJDIR/lib/perl5/Pod/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


From: Robbie Hatley on

Juan Manuel Guerrero wrote:

> (reports of successes and failures on MSDOS, Win98,
> and WinXP)

Thanks for the information, but I don't use those OSs.
All the computers I use both at home and at work run
Microsoft Windows 2000 Professional. (IMO, the only
"good" OS Microsoft ever made.)

Djgpp works fine for me on Win2K machines, with the
exception of the documentation for Perl 5.8.8, all of
which (perldoc, info, man) is broken and useless.
(Perldoc.pm crashes w complaints of not being able to
write temporary files; and the man pages cause ntvdm.exe
to crash w "illegal memory access" if you try to read
them. As for the info pages, there aren't any.)

I don't know if this is true on all Win2K machines,
but it's true on the 2 machines I've tried so far.
Unknown if it's fixable at this point; I'm still
struggling with it.

--
Cheers,
Robbie Hatley
lonewolf aatt well dott com
www dott well dott com slant user slant lonewolf slant


From: A. Sinan Unur on
"Robbie Hatley" <see.my.signature(a)for.my.email.address> wrote in
news:hZmdnUQdD63UrZTVnZ2dnUVZ_h6hnZ2d(a)giganews.com:

> Juan Manuel Guerrero wrote:
>
>> (reports of successes and failures on MSDOS, Win98,
>> and WinXP)
>
> Thanks for the information, but I don't use those OSs.
> All the computers I use both at home and at work run
> Microsoft Windows 2000 Professional. (IMO, the only
> "good" OS Microsoft ever made.)

Opinions vary on that ;-)

I'll give it a shot on my office computer on Monday.

Incidentally, could you tell me the service pack level for your
Win2K installation?

> Djgpp

Not to start another flamewar over names, but I don't think DJ
appreciates his name being mangled like that.

http://www.delorie.com/users/dj/

Sinan
--
A. Sinan Unur <1usa(a)llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)

comp.lang.perl.misc guidelines on the WWW:
http://www.rehabitation.com/clpmisc/
From: Ben Bullock on
On Sat, 19 Apr 2008 00:41:44 +0000, A. Sinan Unur wrote:

> Not to start another flamewar over names, but I don't think DJ
> appreciates his name being mangled like that.
>
> http://www.delorie.com/users/dj/

That made me laugh, because it says "It is not correct to insert a space
between the D and the J, or to put periods after them as if they were
initials, or to make either of them lower case" but the title of the page
is "dj delorie" in lower case, and the top graphical bar also says "dj
delorie" in lower case.