#169 dunecontrol does not work with MacOS

Metadata

Property	Value
Reported by	Markus Blatt (markus@dr-blatt.de)
Reported at	Aug 8, 2006 10:10
Type	Bug Report
Version	Git (pre2.4) [autotools]
Operating System	Mac OS
Last edited by	Jö Fahlke (jorrit@jorrit.de)
Last edited at	Aug 9, 2006 08:47
Closed by	Markus Blatt (markus@dr-blatt.de)
Closed at	Aug 10, 2006 12:26
Closed in version	1.0
Resolution	Fixed
Comment	Changing the sed statement fixed this bug.

Description

Quoted from Benedikt's mail:

as I am currently trying to install Dune on Mac OS C I have encountered some problems.

oswalds-powerbook59:~/dune oswald$ ./dune-common/bin/dunecontrol --opts=dune.macosx.opts.txt all ./dune-common/bin/dunecontrol: eval: line 3: syntax error near unexpected token `autogen'

Joe idenitified the problem more closely:

There is only one multi line eval statment in dunecontrol, at line 290:

======================================================================

We need to run this via eval in order construct the case for the commands

eval ' case "$command" in '$(echo $COMMANDS | sed -e 's/ +/ | /g')') find_modules_in_path

In addition to what Markus said, can you please send the output of the shell commands

COMMANDS="update autogen configure make all exec svn"

echo $COMMANDS | sed -e 's/ +/ | /g'

echo $COMMANDS | sed -e 's/ / | /g'

echo $COMMANDS | sed 's/ +/ | /g'

echo $COMMANDS | sed 's/ / | /g'

echo $COMMANDS | sed 's/ /|/g'

(The "+" should not really be neccessary since "echo $COMMAND" will fold every whitespace in $COMMAND into one space character. For the "-e", it is also not neccessary, and I remember some autoconf doku on portable shell stating that it can actually be harmful on some platforms.)