Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: bernd.kuhls@t-online.de, chrismcc@gmail.com,
	yann.morin.1998@free.fr, buildroot@buildroot.org,
	fontaine.fabrice@gmail.com, markus.mayer@broadcom.com
Subject: Re: [Buildroot] [PATCH] package/linux-tools: fix PCI endpoint tests build with recent kernels
Date: Thu, 22 Oct 2026 11:35:08 -0700	[thread overview]
Message-ID: <94786551-afda-4d20-b259-6ca2b8ffd05c@broadcom.com> (raw)
In-Reply-To: <atpWByZNXAvK-Cgg@windsurf>

On 10/22/26 11:30, Thomas Petazzoni wrote:
> On Thu, Oct 22, 2026 at 11:02:41AM -0700, Florian Fainelli wrote:
> 
>>> Hm is this thread dependency new? With the Linux 6.14 change, or
>>> unrelated?
>>
>> I looked at the Makefile and because it linked with libpthread I assumed it
>> needed it, but the source code reveals that it does not actually, just sent
>> this out:
>>
>> https://lore.kernel.org/all/20261022180022.1282641-1-florian.fainelli@broadcom.com/
> 
> Saw your patch. Problem is that all kernels from 6.14 to 7.4 at least
> will require pthread to build the pci endpoint tests. So in the end, I
> suggest that we keep your thread dependency.
> 
> Not a big deal as 99.99% of people will use a configuration that has
> threads enabled. Better that than having random build failures from
> time to time in our autobuilders.

v2 explicitly passes the libraries to link against, so that should avoid 
the dependency upon the patch above.

> 
>> Yes we certainly can do that, it's more concise, v2 on its way.
> 
> Thanks a lot!
> 
> Thomas


-- 
Florian
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-22 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 17:27 [Buildroot] [PATCH] package/linux-tools: fix PCI endpoint tests build with recent kernels Florian Fainelli via buildroot
2026-10-22 17:33 ` Florian Fainelli via buildroot
2026-10-22 17:40 ` Thomas Petazzoni via buildroot
2026-10-22 18:02   ` Florian Fainelli via buildroot
2026-10-22 18:30     ` Thomas Petazzoni via buildroot
2026-10-22 18:35       ` Florian Fainelli via buildroot [this message]
2026-10-22 19:02         ` Thomas Petazzoni 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=94786551-afda-4d20-b259-6ca2b8ffd05c@broadcom.com \
    --to=buildroot@buildroot.org \
    --cc=bernd.kuhls@t-online.de \
    --cc=chrismcc@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=markus.mayer@broadcom.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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