< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] Missing definition for DEPS_PYTHON



On 26/01/14 11:57, Daniel Pocock wrote:
> 
> 
> On 23/01/14 22:57, Daniel Petrie wrote:
>> I get the same thing.  That is how I originally ran into this problem.
>>
>> bash$ ./configure --with-ssl --with-repro --enable-repro-plugins
>>
>> ...
>> checking whether byte ordering is bigendian... no
>> checking for struct sockaddr_in.sin_len... no
>> ./configure: line 16315: syntax error near unexpected token `DEPS_PYTHON,'
>> ./configure: line 16315: ` PKG_CHECK_MODULES(DEPS_PYTHON, python >= 2.7)'
> 
> 
> It is not about Python at all, it appears that the macro
> PKG_CHECK_MODULES is missing, many people have had the same problem with
> other projects:
> 
> http://www.coffeecode.net/archives/208-PKG_CHECK_MODULES-syntax-error-near-unexpected-token-DEPS,.html
> 
> 
> PKG_CHECK_MODULES is in the package "pkg-config" on Debian/Ubuntu.
> 
> Using it makes the configure.ac script more concise and readable - but
> it also means people without it get that cryptic error.  If you have
> seen some other project that has 20 lines of code in configure.ac for
> checking each library they use, it is because they do not use
> PKG_CHECK_MODULES.
> 
> Please try "apt-get install pkg-config" and then run the configure
> again.  I'll ask on the autotools list to see if anybody can suggest the
> easiest way to improve this experience for people.
> 
> One option is that I simply delete the PKG_CHECK_MODULES line, then
> people using the Python stuff just have to remember to define
> DEPS_PYTHON_CFLAGS and DEPS_PYTHON_LIBS on the configure command line
> and nothing will check that they have a suitable version.
> 

One other observation: this specific error (with Python not selected)
should only be a problem for developers building from the repository or
re-executing autoreconf after expanding the tarball.

When we make a release tarball, the PKG_CHECK_MODULES macro is copied
into the generated configure script

Those using the tarball will need /usr/bin/pkg-config (also from the
pkg-config package) but only if they actually select Python support.