From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: qemu: Make dependency to nettle explicit
Date: Thu, 12 Sep 2019 08:33:38 +0200 [thread overview]
Message-ID: <20190912083338.1e2fdfd3@windsurf> (raw)
In-Reply-To: <20190911084039.16983-1-post@lespocky.de>
Hello Alexander,
On Wed, 11 Sep 2019 10:40:39 +0200
Alexander Dahl <post@lespocky.de> wrote:
> For the fli4l router distribution we had problems building 'qemu', some
> builds failed complaining when checking dynamic linking of the package:
>
> >>> qemu 2.12.1 Error: Library libnettle.so.6 referenced by usr/libexec/qemu-bridge-helper belongs to package nettle which is not a dependency of qemu
>
> https://web.nettworks.org/ci/job/fli4l/job/buildroot/job/4.0/job/trunk-x86_64/495/console
>
> Making the dependency explicit, by calling ./configure with
> --enable-nettle or --disable-nettle depending on the activation status
> of package nettle, solves the issue.
>
> For fli4l the fix is still based on buildroot 2018.02.x, but the problem
> is the same in recent version of buildroot, and the fix works for master
> as well.
>
> Cc: Florian Wolters <florian@florian-wolters.de>
> Signed-off-by: Alexander Dahl <post@lespocky.de>
Thanks for the patch, which looks good. I have one question though:
what prints the message "Error: Library libnettle.so.6 referenced by
usr/libexec/qemu-bridge-helper belongs to package nettle which is not a
dependency of qemu". It seems like a check from Buildroot, but I can't
find it in our tree, and I don't remember we had such a check. Maybe
it's just because it's early and my eyes are not well opened and I'm
missing something obvious.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-12 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 8:40 [Buildroot] [PATCH] package: qemu: Make dependency to nettle explicit Alexander Dahl
2019-09-12 6:33 ` Thomas Petazzoni [this message]
2019-09-12 7:45 ` Alexander Dahl
2019-09-15 13:22 ` Thomas Petazzoni
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=20190912083338.1e2fdfd3@windsurf \
--to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox