From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] DJGPP: fnchange.lst removal attempt
Date: Mon, 12 Apr 2010 17:48:00 -0000 [thread overview]
Message-ID: <83vdbwy33r.fsf@gnu.org> (raw)
In-Reply-To: <20100412000856.GA25681@host0.dyn.jankratochvil.net>
> Date: Mon, 12 Apr 2010 02:08:56 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> tried to create a script to autogenerate and remove fnchange.lst
Thanks for doing this.
> but ... after
> writing it I found I am not able to even compile the current FSF GDB HEAD.
Don't worry about that. You can test the output of the script in a
different, much easier way: use the ARI script to check that no
file-name conflicts are reported by it after you update fnchange.lst.
That way, you don't need to set up a DOS system.
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).
> fnchange.lst change of directory names:
> @V@/gdb/testsuite/gdb.gdbtk/EVERYTHING @V@/gdb/testsuite/gdb.tk/EVERYTHING
That's because we also have gdb/testsuite/gdb.gdb and
gdb/testsuite/gdb.gdbserver, which clash with it.
> Also current gdb/config/djgpp/djconfig.sh cannot find gdb/ChangeLog.002 .
Can you see why this happens? gdb/ChangeLog.002 should have been
produced by renaming gdb/ChangeLog-2002, by this line in fnchange.lst:
@V@/gdb/ChangeLog-2002 @V@/gdb/ChangeLog.002
> In this state I find all the adjustments of gdb/config/djgpp/fnchange.lst not
> much useful.
It worked for me during GDB 7.0 pretest. But I agree that maintaining
it by hand is annoying and error-prone. So I'm very much in favor of
producing it with a script.
Thanks.
next prev parent reply other threads:[~2010-04-12 17: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 [this message]
2010-04-12 20:05 ` Joel Brobecker
2010-04-12 20:48 ` Jan Kratochvil
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=83vdbwy33r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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