bug-automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: automake-1.11.1 test results on old OSF/1


From: Stefano Lattarini
Subject: Re: automake-1.11.1 test results on old OSF/1
Date: Thu, 19 Aug 2010 23:48:28 +0200
User-agent: KMail/1.13.3 (Linux/2.6.30-2-686; KDE/4.4.4; i686; ; )

On Thursday 19 August 2010, Jay K wrote:
> > Is your /bin/sh a Korn Shell in disguise?
> How do I know?
I honestly don't know, I hoped you already knew that somehow.

Anyway, this is how I can see that Solaris 10 /usr/xpg4/bin/sh is really
just a Korn shell in disguise (maybe compiled with some switches to turn
off Korn extensions and enhance Bourne-compatibility):
 $ strings /usr/xpg4/bin/sh | grep '@(#)'
 @(#)Version M-11/16/88i
 $ strings /bin/ksh | grep '@(#)'
 @(#)Version M-11/16/88i

Maybe you can do something like:
  $ strings /bin/sh | egrep '@.*#|Version'
  $ strings /bin/ksh | egrep '@.*#|Version'
and see which the outputs are, and what they suggest.

Or use the trick explained here:
  
<http://unix.ittoolbox.com/groups/technical-functional/shellscript-l/command-to-find-the-version-of-ksh-1490264>
which reads:
 """
  To get the Ctrl-V function to work, you need to be in "vi" mode. To do
  this, type in the following:
    $ set -o vi
  Now simply press and release the "Esc" key one time, then perform a
  Ctrl-V (you have to press and hold the Ctrl key, then press and release
  the v key. Release both keys when you've done this). On Solaris 8 & 10,
  you should see the following:
    $ Version M-11/16/88i
 """

(Disclaimer: the above suggestions are mostly wild guesses, as I have
absolutely no experience with OSF1/Tru64).
 
> > Do you happen to have bash installed on your system?
> Yes.
Good.

> % type bash
> bash is /home/jayk/bin/bash
> 
> % bash --version
> GNU bash, version 4.1.7(1)-release (alphaev67-dec-osf5.1)
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html> ...
And very modern too (newer then mine).

>  > If yes, could you try to run the following 
> Yes, later.
OK, thank you very much. 

Regards,
   Stefano



reply via email to

[Prev in Thread] Current Thread [Next in Thread]