public inbox for linux-snps-arc@lists.infradead.org
 help / color / mirror / Atom feed
From: Shahab Vahedi <Shahab.Vahedi@synopsys.com>
To: James Hilliard <james.hilliard1@gmail.com>,
	Shahab Vahedi <Shahab.Vahedi@synopsys.com>
Cc: Arnout Vandecappelle <arnout@mind.be>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>
Subject: Re: [Buildroot] [PATCH v3 1/1] package/bpftool: revert bpf_cookie patch to allow building
Date: Thu, 16 Jun 2022 08:11:07 +0000	[thread overview]
Message-ID: <40fe53f9-cd74-a19f-e338-2aa4d35a9ec1@synopsys.com> (raw)
In-Reply-To: <CADvTj4qcYpo=UB2Qny7-0mXiqq9R0u6QMBgs+9hXm76SQxvEew@mail.gmail.com>

On 6/16/22 01:27, James Hilliard wrote:
> On Wed, Jun 15, 2022 at 5:10 AM Shahab Vahedi via buildroot
> <buildroot@buildroot.org> wrote:
>>
>> 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.
> 
> I think clang/llvm support isn't going to work correctly yet since we only have
> version 9.0.1, there's a series bumping to version 11.1.0 that should fix that:
> https://patchwork.ozlabs.org/project/buildroot/list/?series=291585
> 
> Minimum clang/llvm version for libbpf co-re is version 10:
> https://github.com/libbpf/libbpf*bpf-co-re-compile-once--run-everywhere

You're right about the clang version, but it doesn't have anything to do
with Buildroot's clang. The build process uses the clang that is installed
on the host. For Debian bullseye, that is clang 11.

To emphasise, I am cross-building bpftool for my "arc-linux" target, and yet
the bootstrap part of bpftool, uses the x86 clang of the Debian machine.


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

  reply	other threads:[~2022-06-16  8:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <97ea44bb-58fe-d6cb-6c79-9be0b245f2c6@synopsys.com>
2022-06-14  8:26 ` [PATCH v2 1/1] package/bpftool: revert bpf_cookie patch to allow building Shahab Vahedi
2022-06-14  9:31   ` [PATCH v3 " Shahab Vahedi
2022-06-14 17:14     ` Arnout Vandecappelle
2022-06-14 17:27       ` Arnout Vandecappelle
2022-06-15 11:03         ` Shahab Vahedi
2022-06-15 11:10       ` Shahab Vahedi
2022-06-15 23:27         ` [Buildroot] " James Hilliard
2022-06-16  8:11           ` Shahab Vahedi [this message]
2022-06-19 15:20             ` Arnout Vandecappelle
2022-06-19 23:19               ` James Hilliard
2022-06-20  6:45                 ` Arnout Vandecappelle
2022-06-20  9:17                   ` James Hilliard
2022-06-20 18:27                     ` Arnout Vandecappelle
2022-08-09  9:46                       ` James Hilliard
2022-06-15 10:57 ` [Buildroot] [PATCH v4 " Shahab Vahedi
2022-06-24 14:21   ` Shahab Vahedi
2023-02-08 16:36   ` Arnout Vandecappelle
2023-02-09 12:23     ` Shahab Vahedi
2023-02-09 20:27       ` Arnout Vandecappelle
2023-02-10  9:17         ` Shahab Vahedi
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=40fe53f9-cd74-a19f-e338-2aa4d35a9ec1@synopsys.com \
    --to=shahab.vahedi@synopsys.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox