All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shahab Vahedi via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Cc: "linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	Shahab Vahedi <Shahab.Vahedi@synopsys.com>
Subject: Re: [Buildroot] [PATCH v3 1/1] package/bpftool: revert bpf_cookie patch to allow building
Date: Wed, 15 Jun 2022 11:10:06 +0000	[thread overview]
Message-ID: <aafcf149-d0b9-8c95-751c-64ec4dabf5b5@synopsys.com> (raw)
In-Reply-To: <e8be91c7-8597-7a7e-9714-9f8045781959@mind.be>

Hi Arnout,

On 6/14/22 19:14, Arnout Vandecappelle wrote:
> 
> On 14/06/2022 11:31, Shahab Vahedi wrote:
>> Building bpftool on Debian 11 (bullseye) with kernel v5.10 and clang-11
> 
>  How do you build host-bpftool with clang in Buildroot context? HOSTCC is set to gcc in the Makefile... Do you supply an explicit HOSTCC= on the Buildroot command line? I'm not sure if we are really interested in carrying fixes for such exotic and not-really-supported situations...

No, I don't do any sort of trickery to build bpftool on my end. The
bootstrapping, if becomes available for your configuration, uses clang
and only clang. I tried to explain this in v4 of the patch [1], the
second paragraph of the commit message.

[1] [v4,1/1] package/bpftool: revert bpf_cookie patch to allow building
https://patchwork.ozlabs.org/project/buildroot/patch/29d2a8c7-44cd-da42-5fed-f17ec0f8ccf2@synopsys.com/

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

WARNING: multiple messages have this Message-ID (diff)
From: Shahab Vahedi <Shahab.Vahedi@synopsys.com>
To: Arnout Vandecappelle <arnout@mind.be>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Cc: "linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	Shahab Vahedi <Shahab.Vahedi@synopsys.com>
Subject: Re: [PATCH v3 1/1] package/bpftool: revert bpf_cookie patch to allow building
Date: Wed, 15 Jun 2022 11:10:06 +0000	[thread overview]
Message-ID: <aafcf149-d0b9-8c95-751c-64ec4dabf5b5@synopsys.com> (raw)
In-Reply-To: <e8be91c7-8597-7a7e-9714-9f8045781959@mind.be>

Hi Arnout,

On 6/14/22 19:14, Arnout Vandecappelle wrote:
> 
> On 14/06/2022 11:31, Shahab Vahedi wrote:
>> Building bpftool on Debian 11 (bullseye) with kernel v5.10 and clang-11
> 
>  How do you build host-bpftool with clang in Buildroot context? HOSTCC is set to gcc in the Makefile... Do you supply an explicit HOSTCC= on the Buildroot command line? I'm not sure if we are really interested in carrying fixes for such exotic and not-really-supported situations...

No, I don't do any sort of trickery to build bpftool on my end. The
bootstrapping, if becomes available for your configuration, uses clang
and only clang. I tried to explain this in v4 of the patch [1], the
second paragraph of the commit message.

[1] [v4,1/1] package/bpftool: revert bpf_cookie patch to allow building
https://patchwork.ozlabs.org/project/buildroot/patch/29d2a8c7-44cd-da42-5fed-f17ec0f8ccf2@synopsys.com/

-- 
Shahab
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

  parent reply	other threads:[~2022-06-15 11:10 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 21:30 [Buildroot] [PATCH] package/bpftool: revert bpf_cookie patch to allow building Shahab Vahedi via buildroot
2022-06-14  8:26 ` [Buildroot] [PATCH v2 1/1] " Shahab Vahedi via buildroot
2022-06-14  8:26   ` Shahab Vahedi
2022-06-14  9:31   ` [Buildroot] [PATCH v3 " Shahab Vahedi via buildroot
2022-06-14  9:31     ` Shahab Vahedi
2022-06-14 17:14     ` [Buildroot] " Arnout Vandecappelle
2022-06-14 17:14       ` Arnout Vandecappelle
2022-06-14 17:27       ` [Buildroot] " Arnout Vandecappelle
2022-06-14 17:27         ` Arnout Vandecappelle
2022-06-15 11:03         ` [Buildroot] " Shahab Vahedi via buildroot
2022-06-15 11:03           ` Shahab Vahedi
2022-06-15 11:10       ` Shahab Vahedi via buildroot [this message]
2022-06-15 11:10         ` Shahab Vahedi
2022-06-15 23:27         ` [Buildroot] " James Hilliard
2022-06-15 23:27           ` James Hilliard
2022-06-16  8:11           ` Shahab Vahedi via buildroot
2022-06-16  8:11             ` Shahab Vahedi
2022-06-19 15:20             ` Arnout Vandecappelle
2022-06-19 15:20               ` Arnout Vandecappelle
2022-06-19 23:19               ` James Hilliard
2022-06-19 23:19                 ` James Hilliard
2022-06-20  6:45                 ` Arnout Vandecappelle
2022-06-20  6:45                   ` Arnout Vandecappelle
2022-06-20  9:17                   ` James Hilliard
2022-06-20  9:17                     ` James Hilliard
2022-06-20 18:27                     ` Arnout Vandecappelle
2022-06-20 18:27                       ` Arnout Vandecappelle
2022-08-09  9:46                       ` James Hilliard
2022-08-09  9:46                         ` James Hilliard
2022-06-15 10:57 ` [Buildroot] [PATCH v4 " Shahab Vahedi via buildroot
2022-06-15 10:57   ` Shahab Vahedi
2022-06-24 14:21   ` Shahab Vahedi via buildroot
2022-06-24 14:21     ` Shahab Vahedi
2023-02-08 16:36   ` Arnout Vandecappelle
2023-02-08 16:36     ` Arnout Vandecappelle
2023-02-09 12:23     ` Shahab Vahedi via buildroot
2023-02-09 12:23       ` Shahab Vahedi
2023-02-09 20:27       ` Arnout Vandecappelle
2023-02-09 20:27         ` Arnout Vandecappelle
2023-02-10  9:17         ` Shahab Vahedi via buildroot
2023-02-10  9:17           ` Shahab Vahedi
2023-02-10 13:12           ` Arnout Vandecappelle
2023-02-10 13:12             ` Arnout Vandecappelle

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=aafcf149-d0b9-8c95-751c-64ec4dabf5b5@synopsys.com \
    --to=buildroot@buildroot.org \
    --cc=Shahab.Vahedi@synopsys.com \
    --cc=arnout@mind.be \
    --cc=linux-snps-arc@lists.infradead.org \
    /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.