Help with GNAT install

Help with GNAT install

[Jason Carley]

Hi all,

I am trying to get the Win95/NT version of GNAT 3.09 running under
Win95.  All is fine except that gnatchop will not work.  It this a bug
with the install or a bug with the installer?

Regards,


Jason.

Re: Help with GNAT install

[Philip Brashear]

In article <33b4d855.2425807@news.magna.com.au>,
Jason Carley <jcarley@magna.com.au> wrote:
>Hi all,
>
>I am trying to get the Win95/NT version of GNAT 3.09 running under
>Win95.  All is fine except that gnatchop will not work.  It this a bug
>with the install or a bug with the installer?
>
>Regards,
>
>
>Jason.

I noticed that when the files are unzipped, the text files are left with
Unix-style <LF> line separators instead of being converted to DOS-style
<CR><LF> markers.  (I view this as an oversight error on the part of the
people doing the packaging.)

Solution: Use the DOS "EDIT" command to edit gnatchop.bat.  Save the file
and exit the editor.  Edit fixes up the line separators, so gnatchop 
should work like a charm.

Good luck!

Phil Brashear
EDS Incorporated

Re: Help with GNAT install

[Robert Dewar]

Phil Brashear says

<<Solution: Use the DOS "EDIT" command to edit gnatchop.bat.  Save the file
and exit the editor.  Edit fixes up the line separators, so gnatchop
should work like a charm.
>>

This has been discussed a number of times, both here and on chat@gnat.com.
I strongly recommend that GNAT users looking for help subscribe to 
chat@gnat.com. A lot of knowledgable GNAT users willing to help others
hang out there who do not feel they have time to read CLA (fancy that :-)

To subscribe, send email to chat-request@gnat.com with a subscribe
message giving your email address.

Note: this glitch with gnatchop.bat is a perfect example of the kind of
thing that we would like to avoid in a public release. Obviously this
kind of thing causes no trouble to the small set of customers using the
system. First of all, they mostly know what they are doing, so, like
Phil, they can easily fix the problem themselves. Second, if they do
have a problem, we can immediately fix it for them.

But some user of the public version, often having got the system from
a friend, often without any docuemntation at all, may be quite confused
by such a glitch.

Actually the NT 3.09 version release was a little premature. We rushed it
to meet the deadline for the STC CD COM. Whether that was a good idea,
who knows? On the one hand, it means that people getting that CD ROM
do have a considerably improved version of GNAT for NT/Win95. On the
other hand, there were a couple of glitches like the one Phil refers to.

Probably we should have waited an extra month or so, but it is always easier
to make these judgments in retrospect rather than at the time :-)
Anyway, we are going to try to make very sure that the 3.10 distribution
is in good shape before the public release. So far, the experience with
3.10a looks very encouraging, so we are hoping for a relativly early
public release if all continues to go well.

Re: Help with GNAT install

[Jason Carley]

On 1 Jul 1997 09:01:01 -0400, dewar@merv.cs.nyu.edu (Robert Dewar)
wrote:

>Phil Brashear says
>
><<Solution: Use the DOS "EDIT" command to edit gnatchop.bat.  Save the file
>and exit the editor.  Edit fixes up the line separators, so gnatchop
>should work like a charm.
>>>
>
>This has been discussed a number of times, both here and on chat@gnat.com.
>I strongly recommend that GNAT users looking for help subscribe to 
>chat@gnat.com. A lot of knowledgable GNAT users willing to help others
>hang out there who do not feel they have time to read CLA (fancy that :-)
>

Thanks for the tip Robert.  I have subscribed and the list seems very
useful.

>
>Note: this glitch with gnatchop.bat is a perfect example of the kind of
>thing that we would like to avoid in a public release. Obviously this
>kind of thing causes no trouble to the small set of customers using the
>system. First of all, they mostly know what they are doing, so, like
>Phil, they can easily fix the problem themselves. Second, if they do
>have a problem, we can immediately fix it for them.

With respect, I don't know that a glitch in the system neccesarily
implies that I do not know what I am doing!  I have used Ada95
extensively.  My experience with GNAT under Win95 is not great
however.  Th fix is not exactly intuitive IMHO.

>
>But some user of the public version, often having got the system from
>a friend, often without any docuemntation at all, may be quite confused
>by such a glitch.

On the Walnut Creek Ada CDROM actually.  Please feel free to point me
to the section in the documentation sugesting a fix for this "glitch".

>Probably we should have waited an extra month or so, but it is always easier
>to make these judgments in retrospect rather than at the time :-)
>Anyway, we are going to try to make very sure that the 3.10 distribution
>is in good shape before the public release. So far, the experience with
>3.10a looks very encouraging, so we are hoping for a relativly early
>public release if all continues to go well.
>

Robert, I think that you are using my innocent query as a vehicle to
make a somewhat less than innocent point!  The issue is that there was
a problem with the release.  It doesn't neccesarily mean that 3.10
should be delayed! :-)


Regards,


Jason.