autoconf 2.69?

2013-03-27 Thread Roman Rakus
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. bash uses an earlier version of autoconf, preventing its being built. Is there any plan to upgrade to version 2.69. Looking at devel branch it is using 2.68. RR

rename directory and internal pwd command.

2013-03-27 Thread Masato Asou
Hello, I am useig bash-3.2.25 on CentOS. $ bash --version bash --version GNU bash, version 3.2.25(1)-release (x86_64-redhat-linux-gnu) Copyright (C) 2005 Free Software Foundation, Inc. 1. Go to directory ~/src. $ cd ~/src 2. Rename the directory to ~/src-old. $ mv ~/src ~/src-old 3. Invo

Re: autoconf 2.69?

2013-03-27 Thread Mike Frysinger
On Wednesday 27 March 2013 11:44:32 Roman Rakus wrote: > Support for the ARM 64 bit CPU architecture (aarch64) was introduced in > autoconf 2.69. bash uses an earlier version of > autoconf, preventing its being built. are you talking about config.{sub,guess}, or something else ? -mike signature

Re: rename directory and internal pwd command.

2013-03-27 Thread Bob Proulx
Masato Asou wrote: > 1. Go to directory ~/src. > $ cd ~/src > 2. Rename the directory to ~/src-old. > $ mv ~/src ~/src-old > 3. Invoke pwd command. Then print /home/asou/src by pwd command. > $ pwd > /home/asou/src > 4. Invoke /bin/pwd command. Then print /home/asou/src-old. > $

Re: autoconf 2.69?

2013-03-27 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/27/13 1:07 PM, Mike Frysinger wrote: > On Wednesday 27 March 2013 11:44:32 Roman Rakus wrote: >> Support for the ARM 64 bit CPU architecture (aarch64) was introduced in >> autoconf 2.69. bash uses an earlier version of >> autoconf, preventing its

weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Linda Walsh
Not sure if this is the correct forum for this, as I am very uncertain that it is a bash-bug and am more inclined to believe it is some odd interpretation causing my code to go hay-wire in this instance. So if I should move this to another discussion location, I'm fine with that -- I'm just trying

Re: weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Greg Wooledge
On Wed, Mar 27, 2013 at 11:29:38AM -0700, Linda Walsh wrote: > include lib/Util/Needroot.shh > > where include is a function the name of a file in my path (or an alias > to define the function)... > > > /home/law/bin/recycle_space: line 7: lib/Util/needroot.shh: division by > 0 (error token is "

Re: weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Linda Walsh
Greg Wooledge wrote: > We would need to see the definition of the "include" function, and the > contents of the file that it's presumably sourcing or whatever. > Working on packaging, but to answer your immediate questions: Assuming attachments work, 'include' is in ~/bin Note, some of these fi

Re: weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Greg Wooledge
On Wed, Mar 27, 2013 at 12:17:21PM -0700, Linda Walsh wrote: > dcl -xa _FPATH Arrays cannot be exported. The bash manual explicitly says so: Array variables may not (yet) be exported. > } | ( ((!(remove||expire))) && hsort -s || cat) Use of the && and || operators together as a "shorthan

Re: weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Linda Walsh
Greg Wooledge wrote: > On Wed, Mar 27, 2013 at 12:17:21PM -0700, Linda Walsh wrote: >> dcl -x _SPATH >> dcl -xa _FPATH >> dcl -xA _INC > > Arrays cannot be exported. The bash manual explicitly says so: > > Array variables may not (yet) be exported. === It is there for the 'yet' p

Re: weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Greg Wooledge
On Wed, Mar 27, 2013 at 01:25:53PM -0700, Linda Walsh wrote: > Greg Wooledge wrote: > > Arrays cannot be exported. The bash manual explicitly says so: > > > > Array variables may not (yet) be exported. > === > It is there for the 'yet' part. In "aliases.sh" which > defines the 'includ

Re: weird problem -- path interpretted/eval'd as numeric expression

2013-03-27 Thread Linda Walsh
Greg Wooledge wrote: > On Wed, Mar 27, 2013 at 01:25:53PM -0700, Linda Walsh wrote: >> Greg Wooledge wrote: >>> Arrays cannot be exported. The bash manual explicitly says so: >>> >>> Array variables may not (yet) be exported. >> === >> It is there for the 'yet' part. In "aliases.sh" w

Re: autoconf 2.69?

2013-03-27 Thread Mike Frysinger
On Wednesday 27 March 2013 14:02:57 Chet Ramey wrote: > On 3/27/13 1:07 PM, Mike Frysinger wrote: > > On Wednesday 27 March 2013 11:44:32 Roman Rakus wrote: > >> Support for the ARM 64 bit CPU architecture (aarch64) was introduced in > >> autoconf 2.69. bash uses an earlier version of > >> autocon

Re: autoconf 2.69?

2013-03-27 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/27/13 6:29 PM, Mike Frysinger wrote: > not that i'm against upstream people from updating their autotool versions. Sure, but honestly it's not the highest thing on my list. - -- ``The lyf so short, the craft so long to lerne.'' - Chaucer

Re: rename directory and internal pwd command.

2013-03-27 Thread Masato Asou
From: Bob Proulx Date: Wed, 27 Mar 2013 11:20:35 -0600 > Masato Asou wrote: >> 1. Go to directory ~/src. >> $ cd ~/src >> 2. Rename the directory to ~/src-old. >> $ mv ~/src ~/src-old >> 3. Invoke pwd command. Then print /home/asou/src by pwd command. >> $ pwd >> /home/asou/src >>

Re: Assignments preceding "declare" affect brace and pathname expansion.

2013-03-27 Thread Dan Douglas
On Tuesday, March 26, 2013 08:33:52 PM Chet Ramey wrote: Thank you. I'm familiar with the declaration commands. It's issue 7, not TC1. > arguments are expanded as normal and then treated as the command > does its arguments. Are you saying here that even when a declaration command is _not_ identi