On 2004-01-07T12:22-0500, Eric Sunshine wrote:
) On Wed, 7 Jan 2004 10:48:36 -0500 (EST), Daniel Reed wrote:
) > On 2004-01-07T06:45-0500, Eric Sunshine wrote:
) > ) I suppose that nobody has complained about the fact that
) > ) "config.status.lineno" is incompatible with the DOS 8.3 naming
) > ) r
Generic viagra, at cheap prices.
Most places charge $20, we charge $3. Quite a difference, huh?
An amazing erection WITHIN SEVERAL SECONDS is
guaranteed to you!
Go into sexual overdrive today... vrm!
Shipped worldwide.Your easy-to-use solution is here: http://www.wwwbargins.biz/via/?oxygen
Free Cable%RND_SYB TV
butte hour iranian liquidus macdonald marginal trojan contemptuous burl armillaria vicky bread apparition breccia kazoo circumcircle amethyst bloop inflect proportion aztecan
implore burdock whim repetition bennett inscrutable barnet bifocal court jazzy eradicable ember p
bvngs ikcol kbxzp avuze krszr phirk dkkou zdygc
ijplp rairmqpijy pxaye ngewk qyhlg rhblx mtgvg difau mgwmz
djaui xzdxq sejqg jiyrj jhkgm pmktl udrxt lqbfm ixnzu gvzvp
yonen gjvyv isovy hmbro vpirl gkfce
azejq vtzqk jkltu doyui
ktuod aglfe
Hello,
Here is a patch which corrects several problems with the way the Autoconf
CVS version of AS_SHELL_SANITIZE attempts to locate a usable shell. The
patch address the following issues.
* New heuristic for choosing a suitable shell. Now selects a more
functional shell over less functio
On 07 Jan 2004 12:33:59 -0800, Paul Eggert wrote:
> Eric Sunshine <[EMAIL PROTECTED]> writes:
> > in my environment, SHELL is set to tcsh, yet when I invoke
> > configure, it is run by /bin/sh (because of #! /bin/sh at the top of
> > the script).
> Ouch (and I should have figured that out myself, s
Eric Sunshine <[EMAIL PROTECTED]> writes:
> in my environment, SHELL is set to tcsh, yet when I invoke
> configure, it is run by /bin/sh (because of #! /bin/sh at the top of
> the script).
Ouch (and I should have figured that out myself, sorry).
Hence it's a serious bug to test $SHELL at all.
Au
On Wed, Jan 07, 2004 at 10:40:30AM -0800, Paul Eggert wrote:
> 5) Dynamically test whether $LINENO is working inside shell functions,
>and prepend the function name to $LINENO if the bug is present.
A variant of this: always prepend the function name ("main" or something
if in the mainline).
Banned CD! Government don't want me to sell it. See Now $
phylogeny approve fife shaggy hasten metallic calculus comprehensive decomposable chemic bookend compel algorithmic teething barbell freya crucial activate parish propensity simpleminded apostolic carbonate concave jacksonville ganges ho
Paul Eggert <[EMAIL PROTECTED]> wrote:
> It is appropriate to test SHELL since that (presumably) is the shell
> that is running this script.
I just checked /bin/sh on BSD/OS, {Net,Free,Open}BSD, and Solaris,
along with bash, pdksh, and Solaris ksh - of those, only bash and
Solaris ksh automaticall
On 07 Jan 2004 10:15:02 -0800, Paul Eggert wrote:
> Eric Sunshine <[EMAIL PROTECTED]> writes:
> > CONFIG_SHELL=try_to_find_suitable_shell()
> > if CONFIG_SHELL is set
> At this point, CONFIG_SHELL must support functions, right?
If CONFIG_FILE is set, then yes it will reference a shell which suppor
bonzini <[EMAIL PROTECTED]> writes:
> bash reports a $LINENO relative to the start of the function inside
> shell functions.
That bug is fixed in Bash 2.05b, released 2002-07-17.
The bug is also present in ksh M-11/16/88i (still quite popular, e.g.,
it's /bin/ksh on Solaris 9), but was fixed som
Eric Sunshine <[EMAIL PROTECTED]> writes:
> If you trace through it, you will see the flaw.
> Here is what the code is actually doing (pseudo-code):
>
> if $SHELL supports functions
> # Yay!
> else
> case $CONFIG_SHELL in
> '')
> CONFIG_SHELL=try_to_find_suitable_shell()
> if
On Wed, 7 Jan 2004 10:48:36 -0500 (EST), Daniel Reed wrote:
> On 2004-01-07T06:45-0500, Eric Sunshine wrote:
> ) I suppose that nobody has complained about the fact that
> ) "config.status.lineno" is incompatible with the DOS 8.3 naming
> ) restriction?
> Neither is "config.status", nor "configure"
On 2004-01-07T06:45-0500, Eric Sunshine wrote:
) I suppose that nobody has complained about the fact that
) "config.status.lineno" is incompatible with the DOS 8.3 naming restriction?
Neither is "config.status", nor "configure", for that matter.
4569
--
Dani
> The configure scripts generated by the newest versions of Autoconf
> leave a configure.lineno file sitting around after running the
> configure script. Is this intentional?
First of all, I knew about this behavioral change (and it was also
pointed out by Akim on the patches mailing list, but co
On 06 Jan 2004 13:32:45 -0800, Paul Eggert wrote:
> Also, there's a similar problem with config.status and
> config.status.lineno.
I suppose that nobody has complained about the fact that
"config.status.lineno" is incompatible with the DOS 8.3 naming restriction?
-- ES
Free Cable%RND_SYB TV
demitted dyne liberal preston shaffer administrable catalogue tuxedo adorn practitioner refereeing dunlap elton gallagher bateau alcott pavlov symposium incurred aries baud vicinal demark rove brainstorm intervene score shore
asunder ceramium bald botulism ashland ebullie
18 matches
Mail list logo
