Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Andreas Kusalananda =?iso-8859-1?B?S+Ro5HJp?= Newsgroups: gnu.bash.bug Subject: Re: declare -g reports as invalid option on MacOS (10.14.6) Bash (5.0.11) Date: Sat, 31 Aug 2019 09:06:35 +0200 Lines: 37 Approved: bug-bash@gnu.org Message-ID: References: <14820bd504a5fa7745aa83f4db7d5829e880675f.camel@sutton-family.net> <20190831070635.GA95117@eeyore.my.domain> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1567235202 14141 209.51.188.17 (31 Aug 2019 07:06:42 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org To: Ray Sutton Envelope-to: bug-bash@gnu.org Mail-Followup-To: Ray Sutton , bug-bash@gnu.org Content-Disposition: inline In-Reply-To: <14820bd504a5fa7745aa83f4db7d5829e880675f.camel@sutton-family.net> User-Agent: Mutt/1.12.1 (2019-06-15) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 62.80.200.187 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20190831070635.GA95117@eeyore.my.domain> X-Mailman-Original-References: <14820bd504a5fa7745aa83f4db7d5829e880675f.camel@sutton-family.net> Xref: csiph.com gnu.bash.bug:15336 On Fri, Aug 30, 2019 at 06:03:37PM -0600, Ray Sutton wrote: > Firstly apologies for not using bashbug, I'm having an issue on a > machine I'm rebuilding and don't have email readily available yet > > The issue is on a late 2013 MBP running MacOS 10.14.6 and > bash -version reports 5.0.11(1)-release (x86-64-apple-darwin18.6.0) > > The error is occuring in my .bash_profile and reports as > > -bash: declare: -g: invalid option > declare usage: declare [-afFirtx] [-p] [name[=value]...] > > Which does not agree with the man page. > > My work MBP (mid 2014) is running exactly the same version of both > MacOS and bash, the problem doesn't occur there > > In both cases bash was installed via brew. > > The behavior seems consistent with the original bash 3 declare > statement persisting after the bash 5 install which seems unlikely. > > Any Advice on how to fix this issue? > > Thanks > > Ray Sutton > It seems likely that you are in fact running /bin/bash (3.2.57(1)-release, from the macOS base system) instead of /usr/local/bin/bash (5.0.11(1)-release, current bash from Homebrew). How do you start your bash login shell?