Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: ylwrap
Date: Thu, 12 May 2005 13:06:00 -0000	[thread overview]
Message-ID: <01c556f2$Blat.v2.4$87fb60c0@zahav.net.il> (raw)
In-Reply-To: <20050511233254.GB10961@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 11 May 2005 19:32:54 -0400)

> Date: Wed, 11 May 2005 19:32:54 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
> 
> > So what do I do for now? wait until we resync with the latest version,
> > or commit my changes in the GDB CVS?  Or maybe something else?
> 
> Hard to say in absence of the proposed changes.  The first thing to do
> is make sure that the latest version in automake is OK, or fix it.

The proposed patches are below; they fix the script's notion of
absolute file names on Windows/DOS.  The latest versions of the
script, both in the released Automake 1.9 and in Automake's CVS,
already include the equivalents of these patches.

Unless you (or someone else) are going to import the latest version of
ylwrap VSN, I'd like to commit these changes to the GDB repository,
since they should be harmless.

TIA


Index: ylwrap
===================================================================
RCS file: /cvs/src/src/ylwrap,v
retrieving revision 1.3
diff -u -r1.3 ylwrap
--- ylwrap	24 Sep 2004 13:21:46 -0000	1.3
+++ ylwrap	12 May 2005 12:57:36 -0000
@@ -31,15 +31,15 @@
 shift
 # Make any relative path in $prog absolute.
 case "$prog" in
- /* | [A-Za-z]:\\*) ;;
- */*) prog="`pwd`/$prog" ;;
+ [\\/]* | [A-Za-z]:[\\/]*) ;;
+ *[\\/]*) prog="`pwd`/$prog" ;;
 esac
 
 # The input.
 input="$1"
 shift
 case "$input" in
- /* | [A-Za-z]:\\*)
+ [\\/]* | [A-Za-z]:[\\/]*)
     # Absolute path; do nothing.
     ;;
  *)
@@ -52,7 +52,7 @@
 
 # We don't want to use the absolute path if the input in the current
 # directory like when making a tar ball.
-input_base=`echo $input | sed -e 's|.*/||'`
+input_base=`echo $input | sed -e 's|.*[\\/]||'`
 if test -f $input_base && cmp $input_base $input >/dev/null 2>&1; then
   input=$input_base
 fi
@@ -75,7 +75,7 @@
 
 cd $dirname
 case "$input" in
- /* | [A-Za-z]:\\*)
+ [\\/]* | [A-Za-z]:[\\/]*)
     # Absolute path; do nothing.
     ;;
  *)
@@ -95,7 +95,7 @@
          # If $2 is an absolute path name, then just use that,
          # otherwise prepend `../'.
          case "$2" in
-	   /* | [A-Za-z]:\\*) target="$2";;
+	   [\\/]* | [A-Za-z]:[\\/]*) target="$2";;
 	   *) target="../$2";;
 	 esac
 	 mv "$1" "$target" || status=$?


  reply	other threads:[~2005-05-12 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 20:03 ylwrap Eli Zaretskii
2005-05-11 20:04 ` ylwrap Andreas Schwab
2005-05-11 20:44   ` ylwrap Daniel Jacobowitz
2005-05-11 23:22     ` ylwrap Eli Zaretskii
2005-05-12  2:18       ` ylwrap Daniel Jacobowitz
2005-05-12 13:06         ` Eli Zaretskii [this message]
2005-05-12 13:06           ` ylwrap Daniel Jacobowitz
2005-05-12 12:42   ` ylwrap 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='01c556f2$Blat.v2.4$87fb60c0@zahav.net.il' \
    --to=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