Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [commit] Fix fnchange.lst
Date: Sun, 20 Sep 2009 19:48:00 -0000	[thread overview]
Message-ID: <83ljk9v1qa.fsf@gnu.org> (raw)
In-Reply-To: <83my4pv78y.fsf@gnu.org>

> Date: Sun, 20 Sep 2009 20:46:53 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: gdb-patches@sourceware.org
> 
> > I don't think you'll have write priviledges. If you want, I can add
> > your key to the authorized_keys, or I can commit the changes for you.
> 
> The latter would be more than enough.  I will see if I can find time
> to craft a script that you wanted.

Here you go.  Save as "chkfnames" and invoke it like this:

    srcdir=FOO tmpdir=BAR ./chkfnames

It will produce the list of problematic files on stdout, together with
the reasons for their inclusion.  tmpdir is used to create an Awk
script that filters out files already renamed by fnchange.lst; you can
remove that script when you are done.

Enjoy.


--------------------------------------
#!/bin/sh

fnchange_lst="${srcdir}"/gdb/config/djgpp/fnchange.lst
fnchange_awk="${tmpdir}"/fnchange.awk

# Transform fnchange.lst into fnchange.awk.  The program DJTAR
# does a textual substitution of each file name using the list.
# Generate an awk script that does the equivalent - matches an
# exact line and then outputs the replacement.

sed -e 's;@[^@]*@[/]*\([^ ]*\) @[^@]*@[/]*\([^ ]*\);\$0 == "\1" { print "\2"\; next\; };' \
    < "${fnchange_lst}" > "${fnchange_awk}"
echo '{ print }' >> "${fnchange_awk}"

( cd "${srcdir}" && find * \
    -name '*.info-[0-9]*' -prune \
    -o -name tcl -prune \
    -o -name itcl -prune \
    -o -name tk -prune \
    -o -name libgui -prune \
    -o -name tix -prune \
    -o -name dejagnu -prune \
    -o -name expect -prune \
    -o -type f -print ) \
| awk -f ${fnchange_awk} | doschk | sed '/The following file names are too long for SysV:/q' | fgrep -v 'The following file names are too long for SysV:'

exit 0


  reply	other threads:[~2009-09-20 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  9:50 Eli Zaretskii
2009-09-19 15:58 ` Joel Brobecker
2009-09-19 17:47   ` Eli Zaretskii
2009-09-20 16:11     ` Joel Brobecker
2009-09-20 17:49       ` Eli Zaretskii
2009-09-20 19:48         ` Eli Zaretskii [this message]
2009-09-21 16:56           ` Joel Brobecker
2009-10-01 17:01           ` Joel Brobecker
2009-10-02 11:43             ` Eli Zaretskii
2009-10-02 15:25               ` Joel Brobecker

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=83ljk9v1qa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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