From: Jim R. <jm...@qu...> - 2005-11-11 22:06:28
|
Will Partain wrote: > > >Hmmm... Well, at least we know it got set. Doing a little test on >this sol10 box: > > partain@slimy% ksh > $ test -e ~/foo > $ type test > test is a shell builtin > $ test -e > ksh: test: argument expected > $ test -e /dev/ptmx > $ echo $? > 0 > $ > > I think you're missing the point; I get the same thing with ksh, when testing in this manner. It's sh that doesn't work. And configure, when run from the command line, even compensates for it (by switching to bash). It just doesn't compensate when ark invokes it. THAT's the wierdest part. >In summary: it makes no sense at all :-( Unless you have some other >program called 'test' in your PATH and it misbehaves in just the right >way... I doubt it. > > Nope. In any case, test is built in to sh as well. >What if you change your <CONFIG-SHELL> setting for solaris to /bin/bash? >I mean, if you've *got* a /bin/bash, I would expect GNU stuff to be >very bash-friendly. > >An unsatisfactory answer... I hate things like this :-) > > I'll try it -- but it won't work. .... nope. Exactly the same, except that the debug output said 'CONFIG_SHELL=/bin/bash'. The patch/whack that I had posted (changing CONFIG_SHELL) *did* work -- but I can't fully explain why (ultimately, in not setting CONFIG_SHELL). Here's another thing that did work: <CONFIG-SHELL></CONFIG-SHELL> this results in the --verbose output showing: CONFIG_SHELL= (as one would expect...) and lets configure choose to use bash, sucessfully. And finally, I figured out I should check this outside of ark. export CONFIG_SHELL=/bin/bash ./configure FAILS! This is an autoconf/python configure issue... it doesn't work like it should. :( |