Mail Archives: djgpp-workers/1999/05/20/15:29:17
> - 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
This is true, and currently I see no workarround for it. The main
problem is, that the configure script parses for instance the
CONFIG_HEADERS variable, which might look like
CONFIG_HEADERS=config.h:config.in
If you configure now on an other drive, configure inserts
the source directory in this filename ($srcdir/config.in)
and then it sed's the ':'. But now the $srcdir has also a
colon! To change this it would be needed to make changes
to autoconf which I haven't the time.
> - 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
I'll recheck it.
> - 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.
It is there already and named patches.418 ! Having this I think it
is not neccesary to have a separate zip with the missing original
gdb sources.
Robert
******************************************************
* email: Robert Hoehne <robert DOT hoehne AT gmx DOT net> *
* Post: Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW: http://www.tu-chemnitz.de/~sho/rho *
******************************************************
- Raw text -