From: Brendan L. <bm...@ri...> - 2010-08-24 15:04:46
|
Hi Haris et. al. >> What am I still not getting right? > > I'm at work on a windows box right now, so I can't test it, but I > think the problem with the above is an extra "-". To pass the short > form of options to autoreconf, the single letter is prefixed by just > "-", e.g.: > > autoreconf -vi > > The long form of the options uses "--", e.g.: > > autoreconf --verbose --install Yup. "autoreconf -vif" is short for "autoreconf --verbose --install --force" whereas "autoreconf --vif" makes the program think you're trying to pass a single option called vif, which doesn't make any sense. I'm with Tim on this one. CMake is much nicer to use, especially for quick private builds such as yours. > Two other things: > 1. Until recently, there was a bug in configure.ac that caused > autoreconf to fail, with an error message "Unrecognized macro: > AC_CHECK_LIB", but if you just ran autoreconf a second time, > everything worked. However that is fixed in the latest git sources. Awesome! What was the problem? --Brendan (who now, apparently, has autoconf on the brain) |