Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [RFC] DJGPP: fnchange.lst removal attempt
Date: Mon, 12 Apr 2010 20:48:00 -0000	[thread overview]
Message-ID: <20100412204821.GA4391@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100412200520.GC19194@adacore.com>

On Mon, 12 Apr 2010 22:05:20 +0200, Joel Brobecker wrote:
> > Btw, I take it that a release tarball will still include the file,
> > right?  I wouldn't want to ask DJGPP users to have Perl installed, and
> > the need to produce the file will complicate the unpacking
> > instructions, which are already quite complicated (see
> > gdb/config/djgpp/README).
> 
> The tarballs are produced using "make -f src-release gdb.tar", so
> the src-release makefile will need to be adjusted accordingly.

I was originally thinking generated fnchange.lst would be even in the
repository as generating the list requires gdb.tar which is difficult to
create.

But it is true it would be fine to generate fnchange.lst at the dist time.
Just the Perl script would be worth adjusting from git to CVS dependency.

But that is not the main point; I should try again to build GDB on DOS.
If no one is able to build it...  I thought Eli Z. builds it regularly.


Thanks,
Jan


  reply	other threads:[~2010-04-12 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12  0:09 Jan Kratochvil
2010-04-12 17:48 ` Eli Zaretskii
2010-04-12 20:05   ` Joel Brobecker
2010-04-12 20:48     ` Jan Kratochvil [this message]
2010-04-12 20:57       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100412204821.GA4391@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox