Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> On Thu, Feb 12, 2004 at 10:29:29AM -0800, Paul Eggert wrote:
> > Yes; autoconf doesn't support \ in file names.
>
> Did you see the separate bit of my message, about _AC_INIT_PREPARE?
> That means that autoconf doesn't support \ in any arguments wh
On Thu, Feb 12, 2004 at 10:29:29AM -0800, Paul Eggert wrote:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
>
> > > $ a='a\b'
> > > $ expr "X$a" : 'X\(.*\)'
> > > a\b
> >
> > That's a neat trick, I didn't know it. Is this in the shell
> > portability guide?
>
> No, because some older version o
Paul Eggert writes:
> Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> > $ a='a\b'
> > $ set | grep '^a='
> > a='a\b'
> > $ echo "$a"
> > a
> > $
> POSIX says that the last echo is equivalent to
>
> $ echo 'a\b'
>
> and that the results are implementation-defined, since 'echo' has
> u
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> > $ a='a\b'
> > $ expr "X$a" : 'X\(.*\)'
> > a\b
>
> That's a neat trick, I didn't know it. Is this in the shell
> portability guide?
No, because some older version of expr can't handle arguments larger
than 120 bytes (this is documented).
> Not
On Thu, Feb 12, 2004 at 01:24:07AM -0800, Paul Eggert wrote:
> > i.e. the \b is processed. This interacts very badly with
> > --program-transform-name='s/g\(.*\)/g\1-3.4/',
>
> Hmm, but your script doesn't necessarily indicate any problem with
> --program-transform-name.
>
> POSIX says that the
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> > ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
> > ac_i=`echo "$ac_i" | sed "$ac_script"`
>
> By the way, something I noticed a few months ago when fixing quoting
> bugs in GCC: this style of code triggers all sorts of problems with dash
> (former
On Wed, Feb 11, 2004 at 12:33:52PM -0800, Paul Eggert wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
> > I've never heard of a shell performing the // -> / substitution
> > indiscriminately.
>
> Me neither.
>
> Autoconf is littered with code like this:
>
> ac_script='s/\$U\././;s/\.o$//;
> Does any Tru64 expert know whether this bug has been fixed in later
> versions, (e.g., Tru64 5.1A) and/or whether it was present in earlier
> versions (e.g., Tru64 5.0A or 4.0G)? Is a patch available for Tru64
> 5.1?
On Tru64 4.0F (OSF1 V4.0 1229 alpha), I get two slashes. The machine has
o
On Wed, 11 Feb 2004, Jim Meyering wrote:
> That's due to a bug in OSF 5.1's /bin/sh.
it's been Tru64 for a few years.
time to upgrade.
> When I ran that same test a few days ago, I found that it would
> pass when invoked using bash, and so I didn't dig any deeper.
> Your report has prompted me t
Jim Meyering <[EMAIL PROTECTED]> writes:
> I've never heard of a shell performing the // -> / substitution
> indiscriminately.
Me neither.
Autoconf is littered with code like this:
ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
ac_i=`echo "$ac_i" | sed "$ac_script"`
This passes an argument wit
On Wed, Feb 11, 2004 at 11:48:09AM +0100, Jim Meyering wrote:
> $ echo / // /// .// //.
> $ echo abc| tr -t ab //
Here's a trivial little debugging aid I can't live without, for
testing and isolating just such things without driving oneself
crazy, or resorting to painful contortions like
$ x=//
$ eval "echo \$x"
/
Okay, I confirm this on spe147.testdrive.hp.com with /bin/sh.
$ echo / // /// .// //.
/ / // /// ./ //.
Confirmed. This also happens with /usr/bin/echo.
$ set -x
$ echo abc| tr -t ab //
+ echo abc
+ tr -t ab /
/bc
Confirmed on the "+" lines,
[EMAIL PROTECTED] (Michael Elizabeth Chastain) wrote:
> I tried coreutils 5.1.3 on hppa2.0w-hp-hpux11.11 and alphaev68-dec-osf5.1.
> I ran into several problems, documented below.
...
Thanks again for the testing and report.
> alphaev68-dec-osf5.1, gnu make 3.79.1, osf cc
>
> configure works
>
13 matches
Mail list logo
