Problem with configure script

[Cameron Horsburgh]

Hi folks,

I'm trying to build from a brand new clone of the git repo but I can't
run the autogen script successfully. I get this:



address@hidden:~/sources/lilypond$ sh autogen.sh
stepmake/aclocal.m4 is newer.  Copying file.
processing .
Running autoconf ...
configure.in:59: warning: AC_REQUIRE: `AC_PROG_CC' was expanded before
it was required
../../lib/autoconf/c.m4:433: AC_LANG_COMPILER(C) is expanded from...
../../lib/autoconf/lang.m4:315: AC_LANG_COMPILER_REQUIRE is expanded from...
../../lib/autoconf/general.m4:2593: AC_COMPILE_IFELSE is expanded from...
aclocal.m4:167: STEPMAKE_COMPILE is expanded from...
configure.in:59: the top level
    Warning: about to run `configure' without arguments.
    arguments on the `autogen.sh' command line
    will be passed to `configure'.

    Invoke with --noconfigure to skip configure step.
Running ./configure ...
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking Package... LILYPOND
checking builddir... /home/cameron/sources/lilypond
checking for stepmake... ./stepmake  (${datarootdir}/stepmake not found)
checking for gmake... no
checking for make... make
checking for find... find
checking for tar... tar
checking for bash... /bin/sh
checking for python... python
checking python version... 2.5.4
checking for python... /usr/bin/python
checking whether compiler understands -pipe... ./configure: line 3709:
syntax error near unexpected token `newline'
./configure: line 3709: `yes:'


and it halts. The configure script is created and run but fails as
shown. I've compared the offending line in that file with a successful
configure script on a another machine, and there are differences:

Doesn't work:

fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
else
  { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi

  if test "x$ac_ct_CC" = x; then
    CC=""
  else
    case $cross_compiling:$ac_tool_warned in
yes:
     ###### This is the line that trips up
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $stepmake_cv_cflags_pipe" >&5
$as_echo "$stepmake_cv_cflags_pipe" >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools
not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host
triplet" >&2;}
ac_tool_warned=yes ;;
esac
    CC=$ac_ct_CC
  fi
else
  CC="$ac_cv_prog_CC"
fi



This does work:

fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
  { $as_echo "$as_me:$LINENO: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
else
  { $as_echo "$as_me:$LINENO: result: no" >&5
$as_echo "no" >&6; }
fi

  if test "x$ac_ct_CC" = x; then
    CC=""
  else
    case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:$LINENO: WARNING: using cross tools not prefixed
with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host
triplet" >&2;}
ac_tool_warned=yes ;;
esac
    CC=$ac_ct_CC
  fi
else
  CC="$ac_cv_prog_CC"
fi


I can probably figure out how to fix the config file, but I'll leave
fixing the real problem to someone else...!


Cheers,

--

Cameron Horsburgh