How to disable python in libnl?

Ben Greear greearb at
Wed Nov 16 15:14:12 EST 2011

On 11/16/2011 02:48 AM, Thomas Graf wrote:
> On Tue, Nov 15, 2011 at 02:48:46PM -0800, Ben Greear wrote:
>> On 11/15/2011 02:30 PM, Yegor Yefremov wrote:
>>> On Tue, Nov 15, 2011 at 7:50 PM, Ben Greear<greearb at>   wrote:
>>>> I'm trying to cross-compile libnl for ARM and I don't
>>>> think I have any need of the python stuff.
>>>> Is there any way to disable libnl's use of python?  I
>>>> didn't see any obvious way to do it in ./configure --help
>>> AFAIK it should be possible since this commit:
> The python modules have never been built by default. They always required to
> manually enter the sub directory and run the script to build and
> install the modules.
> However, configure was looking for a python installation which has been
> removed by b4b853e5e7. At least that was the aim of the commit.
> What kind of issue have you run into while corss compling for ARM?

Configure was finding the host's python, and then trying to link
against some python library and failing because the cross-compiler
cannot link with the host's libraries.

With the patch I sent and explicitly disabling python it
configured and compiled fine.

>> +AC_ARG_ENABLE([python],
>> +       AS_HELP_STRING([--disable-python], [Do not build python related code]),
>> +       [enable_python="$enableval"], [enable_python="yes"])
>> +AM_CONDITIONAL([ENABLE_PYTHON], [test "$enable_python" = "yes"])
>> +
>>   AC_CHECK_LIB([m], [pow], [], AC_MSG_ERROR([libm is required]))
>>   AC_CHECK_LIB([pthread], [pthread_mutex_lock], [], AC_MSG_ERROR([libpthread is required]))
> Yes, something like this is needed when we want to integrate the python
> building and installation into the Makefile process.

Well, if it doesn't cause any problem, please apply the patch.  That
was all I needed to get it cross-compiling.


Ben Greear <greearb at>
Candela Technologies Inc

More information about the libnl mailing list