Moin, it seems that configure wasn't updated in the repo and in fact I remember that we agreed that this is the sane approach. So we should make clear in the build instructions that our process has changed: the first thing to do after getting the source or pulling a change of configure.in is calling "autoconf", not calling "configure".
IMHO we also should remove "configure" from the repository so that it is no longer tracked. Regards, Mathias Am 18.09.2011 09:35, schrieb Raphael Bircher: > Hi all. > > Pavel help me to solve the issue. We have to re run autoconf. I will > commit the new configure > > Greetings Raphael > > Am 18.09.11 09:01, schrieb Raphael Bircher: >> Hi at all >> >> since the last CWS integration from Michael Stahl, I have a build >> braker on my mac. Normaly I succsfully build on this mashine. It fails >> at the ./configure process >> >> My configure settings: >> ./configure --disable-odk --disable-pasf --disable-gtk >> --disable-headless --disable-build-mozilla >> --with-build-version=$OOVERSION-`date +%d-%m-%y` --disable-fontconfig >> --without-nas >> --with-jdk-home=/System/Library/Frameworks/JavaVM.framework/Home >> --with-stlport=no --disable-mediawiki --enable-werror --disable-vba >> --with-num-cpus=2 --with-max-jobs=2 --disable-copyleft >> >> The error message: >> Possible unintended interpolation of @ENABLE_CAIRO_CANVAS in string at >> ./set_soenv line 1638. >> Global symbol "@ENABLE_CAIRO_CANVAS" requires explicit package name at >> ./set_soenv line 1638. >> Execution of ./set_soenv aborted due to compilation errors. >> server3:main server3$ echo $ENABLE_CAIRO_CANVAS >> >> Looks like samething with env Variables is wrong. >> >> Greetings Raphael > >
