From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: [PATCH] net-snmp: disable libnl use
Date: Fri, 11 Mar 2011 16:53:10 +0100 [thread overview]
Message-ID: <4D7A4566.6070607@dresearch.de> (raw)
In-Reply-To: <ild6ma$ton$1@dough.gmane.org>
On 03/11/2011 02:05 PM, Koen Kooi wrote:
> On 11-03-11 12:04, Steffen Sledz wrote:
>> Fixes compile error
>
>> | ./.libs/libnetsnmpmibs.so: undefined reference to `nl_handle_destroy'
>> | ./.libs/libnetsnmpmibs.so: undefined reference to `nl_handle_alloc'
>
>> which occurred sometimes depending on build order (not in clean package
>> only builds).
>
> What features do we loose when disabling netlink support? I'd rather get
> the libnl recipe fixed (e.g. static lib only) instead of hacking the
> dependants.
I'm not sure.
But there is no dependency to libnl. If *libnl was not built before net-snmp* the autotools/configure does not find it. So in that case libnl wasn't used anyway.
Just in case *it was built before* net-snmp tries to use it and hits the mentioned error.
Regards,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-03-11 15:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 11:04 [PATCH] net-snmp: disable libnl use Steffen Sledz
2011-03-11 13:05 ` Koen Kooi
2011-03-11 15:53 ` Steffen Sledz [this message]
2011-03-12 0:05 ` Khem Raj
2011-03-14 7:06 ` Steffen Sledz
2011-03-14 16:39 ` Khem Raj
2011-03-15 9:08 ` Eliminating dependency race-conditions (was Re: [PATCH] net-snmp: disable libnl use) Esben Haabendal
2011-03-15 22:03 ` Denys Dmytriyenko
2011-03-16 5:47 ` Eliminating dependency race-conditions Esben Haabendal
2011-03-16 6:22 ` Python-native dependency in libxml2 Ahsan, Noor
2011-03-16 7:08 ` Khem Raj
2011-03-16 7:28 ` Frans Meulenbroeks
2011-03-16 7:43 ` Khem Raj
2011-03-16 8:00 ` Frans Meulenbroeks
2011-03-16 8:05 ` Martin Jansa
2011-03-16 8:38 ` Ahsan, Noor
2011-03-17 10:40 ` Ahsan, Noor
2011-03-18 7:41 ` Ahsan, Noor
2011-03-18 8:38 ` Martin Jansa
2011-03-18 9:47 ` Koen Kooi
2011-03-18 9:01 ` Frans Meulenbroeks
2011-03-16 6:35 ` Eliminating dependency race-conditions Frans Meulenbroeks
2011-03-15 23:15 ` Eliminating dependency race-conditions (was Re: [PATCH] net-snmp: disable libnl use) Graham Gower
2011-03-17 11:18 ` Phil Blundell
2011-03-17 14:43 ` Esben Haabendal
2011-03-17 14:52 ` Graeme Gregory
2011-03-17 15:24 ` Koen Kooi
2011-03-17 15:07 ` Phil Blundell
2011-03-17 17:52 ` Esben Haabendal
2011-03-17 18:05 ` Phil Blundell
2011-03-17 19:58 ` Esben Haabendal
2011-03-17 21:00 ` Phil Blundell
2011-03-18 5:29 ` Esben Haabendal
2011-03-18 10:26 ` Phil Blundell
2011-03-18 12:14 ` Eliminating dependency race-conditions Esben Haabendal
2011-03-19 0:32 ` Richard Purdie
2011-03-22 9:01 ` Esben Haabendal
2011-03-23 20:31 ` Frans Meulenbroeks
2011-03-19 0:18 ` Eliminating dependency race-conditions (was Re: [PATCH] net-snmp: disable libnl use) Richard Purdie
2011-03-22 9:00 ` Eliminating dependency race-conditions Esben Haabendal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7A4566.6070607@dresearch.de \
--to=sledz@dresearch.de \
--cc=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox