Hi Brian, I've just committed a fix for this:
-if [ `basename $0` = env.sh -a x"$ZSH_VERSION" = x ]; then +if [ x`/bin/basename $0` = xenv.sh -a x"$ZSH_VERSION" = x ]; then You can try it locally in your env.sh. Thanks Mike for the explanation. Whether the old code works or fails depends on which basename is picked up from the PATH. /bin/basename has no options so it doesn't care about the leading "-" while GNU basename has options (--version and --help) so it fails for -/bin/bash. Laca On Fri, 2007-12-21 at 11:26 +0000, Brian Nitz wrote: > I'm getting failures caused by odd bash shell behaviour. > I have the default shell for my user set to /bin/bash. When I login I > see this prompt: > -bash-3.2$ > I don't know why I see the leading "-", but sometimes it breaks env.sh > for me. > > -bash-3.2$ . /opt/jdsbld/bin/env.sh > basename: invalid option -- b > Try `basename --help' for more information. > -bash: [: too many arguments > JDS/Solaris CBE version 1.6.0 built on 2007-11-07 by bnitz at dhcp-226-115 > > I also don't know why this fails only sometimes. After a fresh login it > works fine: > > -bash-3.2$ . /opt/jdsbld/bin/env.sh > JDS/Solaris CBE version 1.6.0 built on 2007-11-07 by bnitz at dhcp-226-115 > Unsetting USER > Unsetting LANG > Setting default C compiler CC=/net/jdsserv/re-tools/i386/SS11/bin/cc > Setting default C++ compiler CXX=/net/jdsserv/re-tools/i386/SS11/bin/CC > Setting 32-bit C compiler CC32=/net/jdsserv/re-tools/i386/SS11/bin/cc > Setting 32-bit C++ compiler CXX32=/net/jdsserv/re-tools/i386/SS11/bin/CC > Setting 64-bit C compiler CC64=/net/jdsserv/re-tools/i386/SS11/bin/cc > Setting 64-bit C++ compiler CXX64=/net/jdsserv/re-tools/i386/SS11/bin/CC > Setting LD=/opt/jdsbld/bin/ld-wrapper > Setting > PATH=/opt/jdsbld/bin:/usr/ccs/bin:/usr/gnu/bin:/usr/bin:/usr/sbin:/bin:/usr/sfw/bin:/net/jdsserv/re-tools/i386/SS11/bin > > But then I login again and sometimes it fails. Did something in the > bash shell change recently? > I wonder if this might be causing the JDS build failures for others? > > Ghee Teo wrote: > > Patrick Ale wrote: > > > >> On Dec 12, 2007 5:09 AM, jijun yu <Jijun.Yu at sun.com> wrote: > >> > >> > >> > >>> My autoconf version is 2.61. > >>> /bash-3.2$ autoconf -V > >>> autoconf (GNU Autoconf) 2.61 > >>> Copyright (C) 2006 Free Software Foundation, Inc. > >>> This is free software. You may redistribute copies of it under the terms > >>> of > >>> the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. > >>> There is NO WARRANTY, to the extent permitted by law. > >>> > >>> Written by David J. MacKenzie and Akim Demaille./ > >>> > >>> > >> *sigh* > >> > >> Yes, this is the same version as I am using as well, this is just insane. > >> I first tried with a clean SXCE77 version, same autoconf version as > >> shipped with CBE > >> I tried to bfu to b79, I compiled the SFWNV gate b79 release and > >> installed the packages (same autoconf version as shipped with CBE and > >> SXCE77) > >> > >> It still fails at the same point. > >> Just a long shot, it can't be failing cause I compile on a 32bit host, > >> right? > >> > >> > > I just installed CBE 1.6 and built SUNWpilot-link.spec on a 32-bit laptop. > > It is compiling smoothly. (I am on 79 though) > > > > What is your PATH? or better still env outout after sourcing > > /opt/jdsbld/bin/env.sh > > > > -Ghee > > > >> Patrick > >> > >> > > > > _______________________________________________ > > desktop-discuss mailing list > > desktop-discuss at opensolaris.org > > > > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org
