All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] libnl: handle all installed libraries
Date: Mon, 26 Oct 2009 19:02:58 +0100	[thread overview]
Message-ID: <1256580178.4186.5.camel@sven> (raw)
In-Reply-To: <878weyf3ca.fsf@macbook.be.48ers.dk>

On Mon, 2009-10-26 at 18:54 +0100, Peter Korsgaard wrote:
> >>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> 
>  Gustavo> Peter Korsgaard wrote:
>  >> commit: http://git.buildroot.net/buildroot/commit/?id=61901bd74a622450139358ea0c0f37d4568ad570
>  >> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>  >> 
>  >> libnl does not only install libnl.so, but also libnl-nf.so,
>  >> libnl-genl.so and libnl-route.so. Change the post-install
>  >> and uninstall hooks to handle these libraries as well.
>  >> 
>  >> Signed-off-by: Sven Neumann <s.neumann@raumfeld.com>
>  >> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> 
>  Gustavo> This broke the current version of the libnl package in buildroot since
>  Gustavo> libnl-* doesn't exist for libnl-1.1 (it's all in libnl.so) thus the
> 
> Uhh, that's no good - Sven?
> 
>  Gustavo> strip fails miserably.
>  Gustavo> Sven: Using git/libnl2 snapshot?

Uh, I am sorry. Looks like we updated libnl to version 2.0 some time ago
and I didn't send this update upstream. If you want I can send you a
patch for this. But since this is not really an upstream release but
just a snapshot, it's probably better to just revert the latest libnl
change. Sorry for the inconvenience.


Sven

  reply	other threads:[~2009-10-26 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  8:19 [Buildroot] [git commit master] libnl: handle all installed libraries Peter Korsgaard
2009-10-26 16:03 ` Gustavo Zacarias
2009-10-26 17:54   ` Peter Korsgaard
2009-10-26 18:02     ` Sven Neumann [this message]
2009-10-26 18:10       ` Peter Korsgaard
2009-10-26 18:10       ` Gustavo Zacarias

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=1256580178.4186.5.camel@sven \
    --to=s.neumann@raumfeld.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.