Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Marcus Hoffmann <bubu@bubu1.eu>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/picotool: fix libusb dependencies
Date: Mon, 22 Jul 2024 14:14:43 +0200	[thread overview]
Message-ID: <20240722141443.28d48442@windsurf> (raw)
In-Reply-To: <20240721173831.2350206-1-fontaine.fabrice@gmail.com>

On Sun, 21 Jul 2024 19:38:31 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> libusb dependencies are wrong since the addition of the package in
> commit f7aac1c008f9c59f8c669bade17864b099221065:
>  - BR2_HOST_GCC_AT_LEAST_4_9 is used instead of
>    BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
>  - BR2_TOOLCHAIN_HAS_THREADS is missing
> 
> Fixes: f7aac1c008f9c59f8c669bade17864b099221065
>  - http://autobuild.buildroot.org/results/22689afc092e33b6e3c1c7ffea0d0e3b5bf76d99
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/picotool/Config.in | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)

Dammit, how could I have left this get through. Thanks for fixing
applied!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-22 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 17:38 [Buildroot] [PATCH 1/1] package/picotool: fix libusb dependencies Fabrice Fontaine
2024-07-22 12:14 ` Thomas Petazzoni via buildroot [this message]
2024-07-22 12:16   ` Marcus Hoffmann via buildroot

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=20240722141443.28d48442@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bubu@bubu1.eu \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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