Date: Tue, 19 Sep 1995 14:59:59 +0100
From: dgardner AT mcsilo DOT ilo DOT dec DOT com (Damien Gardner)
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Problem with crt0 and DOS format files.

Hi,

Originally I thought this was a problem with QDPMI and texinfo and posted
it under such a subject name but here are the results of my poking about:

I had problems running texinfo 3.6.0 (the info.exe file): it would cause a
protection fault if I tried to run it without arguments and even this was
intermittent.  I thought QDPMI was doing it.  It wasn't.

MY SETUP (the config files are shown in total, there are no other lines):

  PC:             Wang 386DX33 with 387
                  16 Mb RAM
                  WD Caviar 2540 HD (50Mb free)
                  Unbranded VGA card (not SVGA)

  CONFIG.SYS:     DEVICE=C:\DOS\HIMEM.SYS

  AUTOEXEC.BAT:   SET DJGPP=c:/dj2b3/djgpp.env
                  PATH C:\DJ2B3\BIN

  DJGPP:          Version 2.00 Beta 3 from ftp.idsoftware.com
                  Source code for texinfo 3.6
                  INFO.EXE built from source code using supplied makefile
                  Changed the USER variable in DJGPP.ENV from "dosuser" to
                      my name: "damien"

This is the good bit:

I do a cold boot.  I run c:\dj2b3\gnu\texinfo3.6\info\info.exe as many times
as I want and it will always fail.  I run symify on info.exe and it tells
me that there's a failure in ___crt0_load_environment_file+460.  I run
info.exe again and it works.  This happens every time.  Info.exe only works
after symify has been run (some of the other DJGPP tools make it work too.)

The cause was my DJGPP.ENV file was save in DOS format with the CR+LF line
endings instead of Unixes LF.

The code for ___crt0_load_environment_file looks like it should handle the
extra '\r' character in DOS but it doesn't do so all the time.

When I add some environment variables to my AUTOEXEC.BAT for GO32TMP and
TEMPDIR (or whatever it is) I get a failure in at offset 471 instead of
460 and sometimes info won't work until I give it a command line argument.

Can anyone else reproduce this "feature"?  Is this a known problem or
should I go log it?

I have provided enough details here to reproduce this little oddity but
if you need anymore, just type...

Seeya,
Damien.