From: Andrew Cagney <ac131313@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: David Carlton <carlton@math.stanford.edu>,
gdb-patches@sources.redhat.com
Subject: Re: Patch for gdb/mi 792
Date: Thu, 24 Oct 2002 11:53:00 -0000 [thread overview]
Message-ID: <3DB841B5.8090409@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1021023075522.13511C-100000@is>
> On Tue, 22 Oct 2002, Andrew Cagney wrote:
>
>
>> s,gdb/testsuite/gdb.c++,gdb/testsuite/gdb.cxx,
>> ...
>> s,gdb/testsuite/gdb.c++/m-static.cc,gdb/testsuite/gdb.cxx/m-static.cc,
>> s,gdb/testsuite/gdb.c++/m-static1.cc,gdb/testsuite/gdb.cxx/m-stat1.cc,
>> s,gdb/testsuite/gdb.c++/m-static.exp,gdb/testsuite/gdb.cxx/m-static.exp,
>> s,gdb/testsuite/gdb.c++/m-static.h,gdb/testsuite/gdb.cxx/m-static.h,
>>
>> but the actual renames never match since the first s/// resulted in:
>>
>> gdb/testsuite/gdb.cxx/m-static.cc
>> gdb/testsuite/gdb.cxx/m-static.exp
>> gdb/testsuite/gdb.cxx/m-static.h
>> gdb/testsuite/gdb.cxx/m-static1.cc
>>
>> being passed to doschk (see src/contrib).
>>
>> I'm not sure how well this compares to the behavior of the actual DJGPP
>> command.
>
>
> The program used to rename the files on the fly (called DJTAR) needs that
> both the directory and each one of the files in that directory be
> mentioned on the rename list.
Ok, I think I've fixed it (David was right about the ari script bug).
I'm now wondering if the check is missing anything else. Eli, are there
any characters that shouldn't appear in the renamed file list. ``+''
for instance.
Andrew
next prev parent reply other threads:[~2002-10-24 18:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 15:42 J. Johnston
2002-10-21 20:06 ` Elena Zannoni
2002-10-22 14:59 ` David Carlton
2002-10-22 15:11 ` Elena Zannoni
2002-10-22 15:19 ` David Carlton
2002-10-22 15:12 ` Andrew Cagney
2002-10-22 15:26 ` David Carlton
2002-10-22 18:05 ` Andrew Cagney
2002-10-22 22:57 ` Eli Zaretskii
2002-10-24 11:53 ` Andrew Cagney [this message]
2002-10-24 12:06 ` Eli Zaretskii
2002-10-24 14:29 ` Andrew Cagney
2002-11-07 13:31 J. Johnston
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=3DB841B5.8090409@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@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