Date: Tue, 18 May 1999 13:51:11 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: gdb 4.18 for DJGPP (alpha)
In-Reply-To: <199905171838.VAA14771@is.elta.co.il>
Message-ID: <Pine.SUN.3.91.990518135037.24330W-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 17 May 1999, Robert Hoehne wrote:

Here are some more comments about gdb418s.zip:

 - The distribution comes with config.cache.  I think this is not a
   good idea, since it might produce subtly incorrect results if
   somebody needs to reconfigure the package.  This file is not
   required to build the distribution, so I suggest to remove it.

 - README.DJGPP says almost nothing about rebuilding from sources.  I
   suggest at least to tell people to read the comments of
   djconfig.sh, or, better still, to add those comments to README.

 - Perhaps it is worthwhile to alert people that /bin/sh.exe is left
   on their disk as a side effect, so that they could remove it if
   they want.  (It would be nice if a solution could be found that
   doesn't require to copy sh.exe to /bin, if at all possible.)

 - The comments in djconfig.sh seem to imply that building the package
   from another drive doesn't work (I didn't try that myself).  If
   this is true, it means that it's impossible to build the package
   when the sources are on a CD-ROM without copying the entire
   distribution to the local hard disk.  It would be nice if this
   limitation could be lifted.

 - Contrary to what djconfig.sh says, I didn't have any problems with
   "ln -s" which required to copy cp.exe to ln.exe.  With Bash 1.14.7
   there is such a problem, but it's in the intl subdirectory which
   doesn't participate in the build; with the new Bash 2.03 I didn't
   see any problems at all.  So perhaps that comment could be removed.

 - I think it might be a good idea to have a separate zip file with
   the rest of the files from GDB distribution that aren't included in
   gdb418s.zip.  Somebody who wants to add a new feature might want to
   look at the other files for implementation ideas and other relevant
   info, and fetching the official distribution from a GNU site is
   tedious and error-prone (since you need to figure out which files
   to overwrite).

 - You might also consider generating diffs against the original GNU
   distribution and including it in gdb418s.zip.  I have found such
   diffs very useful while porting a new release in several cases.

Once again--thanks!