feature indeed.
Nevertheless ./configure created by autotools
should rather not rely on such a border case.
autotools claims to enable portability to a wide
range of existing systems. I.e. systems not as they
are specified today, but as they are installed in
reality.
Two elder Linux plus one
On Tue 24 Apr 2007 23:27:15 NZST +1200, Thomas Schmitt wrote:
I read in my man 1 bash:
for name [ in word ] ; do list ; done
Not:
for name [ in [ word ] ] ; do list ; done
And not:
for name [ in word1 word2 ... wordn ] ; do list ; done
yet it works as expected, or in a way to make it
On Wed, Apr 25, 2007 at 01:13:14AM +1200, Volker Kuhlmann wrote:
I have no old authoritative sh at hand, but a Solaris 2.7 /bin/sh
spits a dummy on an empty item list. I view that as a dumb design (one
would have to enclose for loops in a check for empty item lists), since
corrected.
I don't
Hi,
Greg Wooledge:
http://www.opengroup.org/onlinepubs/007908799/xcu/chap2.html#tag_001_009_004_002
First, the list of words following in will be expanded to generate a list
of items. Then, the variable name will be set to each item, in turn,
and the compound-list executed each time. If no
Greg Wooledge [EMAIL PROTECTED] wrote:
You don't have to perform a separate check for an empty item list. This
is perfectly valid, and will do nothing:
words=
for i in $words; do echo hello, world; done
If Solaris's shell is giving any output or errors from the commands above,
then
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
Greg Wooledge:
http://www.opengroup.org/onlinepubs/007908799/xcu/chap2.html#tag_001_009_004_002
First, the list of words following in will be expanded to generate a list
of items. Then, the variable name will be set to each item, in turn,
and
Hi,
I understand all about writing portable scripts with autoconf,
Could you have a look into our autotools configuration ?
The root directory can be inspected at
http://libburnia.pykix.org/browser/libburn/trunk
Can you spot the reason why our configure gets that
empty loop list ?
A pointer
Hi,
This shell silently ignores for i in ; do something ; done.
But this does not make the code portable
For portability i now apply sed to the generated
./configure.
But as said, a functional port demands a hand-made
system adapter anyway.
I can hardly expect autotools to know about
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
This shell silently ignores for i in ; do something ; done.
But this does not make the code portable
For portability i now apply sed to the generated
./configure.
But as said, a functional port demands a hand-made
system adapter anyway.
Thomas Schmitt [EMAIL PROTECTED] wrote:
Hi,
I understand all about writing portable scripts with autoconf,
Could you have a look into our autotools configuration ?
The root directory can be inspected at
http://libburnia.pykix.org/browser/libburn/trunk
Can you spot the reason why our
and binaries you will need autotools
of at least version 1.7.
Command ./bootstrap on my machine produces a ./configure with
three occurences of for ac_header in:
$ grep 'for ac_header in' ./configure
for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
for ac_header
11 matches
Mail list logo
