[Top][All Lists]

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

Re: portability bug (shell syntax)

From: Peter Selinger
Subject: Re: portability bug (shell syntax)
Date: Fri, 6 Aug 2010 04:09:02 -0300 (ADT)

Sorry, I forgot to answer your last two questions. I do not have
CONFIG_SHELL in my environment, and SHELL contains /bin/bash (even if
I run /bin/sh). 

To anticipate your next question: If I invoke ./configure as:

 CONFIG_SHELL=/bin/sh ./configure

then everything works fine, i.e., I get:

 checking whether the shell understands some XSI constructs... no

and the subsequent compilation (using libtool) works without
errors. So the problem really seems to be as I described. 

-- Peter

Ralf Wildenhues wrote:
> Hi Peter,
> * Peter Selinger wrote on Fri, Aug 06, 2010 at 06:02:42AM CEST:
> > I am using libtool-2.2.10 on a
> > SunOS chase-sun 5.10 Generic_118833-20 sun4u sparc SUNW,Ultra-4
> > 
> > Line 665 of libtool is:
> > 
> >   func_arith_result=$(( $* ))
> > 
> > Apparently this syntax is not portable, as Sun's /bin/sh gives:
> > 
> > ../libtool: syntax error at line 665: `func_arith_result=$' unexpected
> Thanks for the bug report.  configure should actually be creating a
> libtool script with the portable code instead of the faster XSI
> implementation if it determines the shell to not be XSI compliant.
> Can you please show how you invoked configure, the configure output,
> and output of './libtool --config'?  Do you have CONFIG_SHELL, SHELL
> in your environment, and if yes, what do they contain?
> Thanks,
> Ralf

reply via email to

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