All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francis Laniel <flaniel@linux.microsoft.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-04
Date: Fri, 06 May 2022 12:05:30 +0100	[thread overview]
Message-ID: <5818465.lOV4Wx5bFT@pwmachine> (raw)

Hi.


Le jeudi 5 mai 2022, 05:41:36 BST Thomas Petazzoni a écrit :
> Hello,
> 
> Autobuilder failures
> ====================
> 
> Below is a list of build failures reported by the Buildroot autobuilders
> in relation to packages or CPU architectures you are in charge of.
> Please help us improving the quality of Buildroot by investigating those
> build failures and sending patches to fix them.
> 
> Results for the 'master' branch
> -------------------------------
> 
> Build failures related to your packages:
> 
>     arch     |             reason             |                             
>          url
> -------------+--------------------------------+----------------------------
> ----------------------------------------------------- powerpc    |
> host-pahole-73383b3a39afe86... |
> http://autobuild.buildroot.net/results/77e892fc30b45c0ccabac5f785edd3662cd5
> f1e6 powerpc    | host-pahole-73383b3a39afe86... |
> http://autobuild.buildroot.net/results/d71c564994d5722ee20c93f18c85fb779976
> 8319
> 
> 
> Thanks for your contribution to Buildroot!

I think this bug is caused by this line in libbpf.mk:
rm $(HOST_DIR)/include/linux/bpf.h

I already wrote a patch which I think fixes the above issue but I am not really 
happy with it.
Indeed, the tweak consists in removing this file before building the kernel, so 
in linux.mk, rather than in libbpf.mk

I would like to be sure my new patch will solve above issue, so is there a way 
for me to run a build on buildroot builders or to copy their environment?


Best regards.


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

                 reply	other threads:[~2022-05-06 11:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5818465.lOV4Wx5bFT@pwmachine \
    --to=flaniel@linux.microsoft.com \
    --cc=buildroot@buildroot.org \
    --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 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.