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
Paul Eggert wrote:
> 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 with two trailing slashes to 'sed'.
> Does it misbehave too, under OSF/Tru64 5.1?
It cannot possibly and if it d
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
Gary V. Vaughan wrote:
I've used return in a couple of places (twice with an integer return
value),
which I fear may break on old platforms. Otherwise I've assumed that all
shell variables are in global scope, and that positional parameters are
stacked and restored at function call boundaries to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Albert Chin wrote:
| So this means func_infer_tag() is broken in branch-1-5 because it does
| this:
| func_infer_tag () {
| if test -n "$available_tags" && test -z "$tagname"; then
| CC_quoted=
| ...
| # Blanks at the start of
Apologies, all. My missing macro definitions were due to an incomplete
macro directory search path. This is an issue with my build
environment, and not Autoconf-specific.
Sorry,
Scott
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Drummonds,
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
Hi, everyone,
After upgrading my existing build environment to Autoconf 2.54 (it took
a lot of work to get it here from 2.13, and upgrading my not be
possible), I'm getting the following error messages, and I don't know
where to start.
[EMAIL PROTECTED] 1047> autoconf
configure:2675: error: possi
Trying to auto* a project.
$ autoscan --version
autoscan (GNU Autoconf) 2.59
Written by David J. MacKenzie and Akim Demaille.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FI
$ 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
