From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: ARI and DUP filenames
Date: Tue, 19 Feb 2002 09:25:00 -0000 [thread overview]
Message-ID: <6228-Tue19Feb2002192229+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200202191416.OAA09488@cam-mail2.cambridge.arm.com> (message from Richard Earnshaw on Tue, 19 Feb 2002 14:16:04 +0000)
> Date: Tue, 19 Feb 2002 14:16:04 +0000
> From: Richard Earnshaw <rearnsha@arm.com>
>
> I've noticed that the ARI script is whingeing about armnbsd-tdep.c and
> armnbsd-nat.c having a common 8.3 filename representation. OK, but why
> doesn't it spot the fact that arm-linux-nat.c and arm-linux-tdep.c also
> have a common 8.3 format?
Because the latter two (and quite a few others) are automatically
renamed when GDB is unpacked on DOS filesystems; see
gdb/config/djgpp/fnchange.lst. To stop ARI's whining, add suitable
lines to fnchange.lst.
next prev parent reply other threads:[~2002-02-19 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 6:16 Richard Earnshaw
2002-02-19 9:25 ` Eli Zaretskii [this message]
2002-02-19 10:16 ` Richard Earnshaw
2002-02-19 11:22 ` Eli Zaretskii
2002-02-19 11:31 ` Richard Earnshaw
2002-02-19 13:06 ` Andrew Cagney
2002-02-19 23:27 ` 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=6228-Tue19Feb2002192229+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb@sources.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