RE: textutils version 2.1 bug

[Parimi, Venkateshwara Rao]

Thanks for the quick response Bob.
Config is getting /bin/sh but do not know why make does use ksh, am still
under confusion.

That's really nice to here that now sh-utils, textutils and fileutils comes
in one package.
I shall try the new version of coreutils then.

Thanks again!
-Venkatesh

-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Tuesday, July 15, 2003 10:55 AM
To: Parimi, Venkateshwara Rao
Cc: 'address@hidden'
Subject: Re: textutils version 2.1 bug


Parimi, Venkateshwara Rao wrote:
> Here is the snippet of make on a solaris 2.6 machine:
> [...]
> /bin/ksh: syntax error at line 0 : `(' unexpected
> [...]
> Makefile.in should be modified as below:
> /u/parimiv/work/upgrades/textutils-2.1/m4>diff Makefile.in.orig
Makefile.in
> 363c363
> <       (((echo EXTRA_DIST =; \
> ---
> >       ( ( (echo EXTRA_DIST =; \

Thank you for reporting that.  It is much appreciated.  What is the
setting of @SHELL@ from configure?  Here is the result on my system.

  grep @SHELL@ config.status
  s,@SHELL@,/bin/sh,;t t

I am not clued into the details here but let me take a shot in the
dark with a question.  Is there any reason why /bin/sh is not suitable
on your system and /bin/ksh is being used instead?

Also textutils is getting a little bit old.  Could you try with a
newer version of the utils?  The textutils package has been merged
with the fileutils and shellutils packages to create the coreutils
package.  The later coreutils was generated using newer and more
portable versions of the autotools which generated that file.

  http://www.gnu.org/software/coreutils/

The latest version of the coreutils package is here:

  http://ftp.gnu.org/gnu/coreutils/coreutils-5.0.tar.bz2
  (coreutils is the union of fileutils, textutils, and sh-utils)

On my system it still generates the "(((" that you are seeing as a
problem with your ksh.  But it is still best to keep on the later
versions if possible.  And hopefully it will detect and use /bin/sh
instead, assuming that is a POSIX shell on your system.

Bob