[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bccad498-3af2-08f1-8264-cf7b438732d3@kalray.eu>
Date: Mon, 9 Jan 2023 16:30:50 +0100
From: Yann Sionneau <ysionneau@...ray.eu>
To: Jeff Xie <xiehuan09@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>, Albert Ou <aou@...s.berkeley.edu>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>,
Ard Biesheuvel <ardb@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, bpf@...r.kernel.org,
Christian Brauner <brauner@...nel.org>,
devicetree@...r.kernel.org, Eric Biederman <ebiederm@...ssion.com>,
Eric Paris <eparis@...hat.com>, Ingo Molnar <mingo@...hat.com>,
Jan Kiszka <jan.kiszka@...mens.com>,
Jason Baron <jbaron@...mai.com>, Jiri Olsa <jolsa@...nel.org>,
Jonathan Corbet <corbet@....net>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Kees Cook <keescook@...omium.org>,
Kieran Bingham <kbingham@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arch@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-audit@...hat.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-perf-users@...r.kernel.org, linux-pm@...r.kernel.org,
linux-riscv@...ts.infradead.org, Marc Zyngier <maz@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Nick Piggin <npiggin@...il.com>,
Oleg Nesterov <oleg@...hat.com>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Moore <paul@...l-moore.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Peter Zijlstra <peterz@...radead.org>,
Rob Herring <robh+dt@...nel.org>,
Sebastian Reichel <sre@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Waiman Long <longman@...hat.com>,
Will Deacon <will@...nel.org>, Alex Michon <amichon@...ray.eu>,
Ashley Lesdalons <alesdalons@...ray.eu>,
Benjamin Mugnier <mugnier.benjamin@...il.com>,
Clement Leger <clement.leger@...tlin.com>,
Guillaume Missonnier <gmissonnier@...ray.eu>,
Guillaume Thouvenin <gthouvenin@...ray.eu>,
Jean-Christophe Pince <jcpince@...il.com>,
Jonathan Borne <jborne@...ray.eu>,
Jules Maselbas <jmaselbas@...ray.eu>,
Julian Vetter <jvetter@...ray.eu>,
Julien Hascoet <jhascoet@...ray.eu>,
Julien Villette <jvillette@...ray.eu>,
Louis Morhet <lmorhet@...ray.eu>,
Luc Michel <lmichel@...ray.eu>,
Marc Poulhiès <dkm@...aplop.net>,
Marius Gligor <mgligor@...ray.eu>,
Samuel Jones <sjones@...ray.eu>,
Thomas Costis <tcostis@...ray.eu>,
Vincent Chardon <vincent.chardon@...ys-design.com>
Subject: Re: [RFC PATCH 00/25] Upstream kvx Linux port
Hi Jeff,
On 1/9/23 16:11, Jeff Xie wrote:
> On Mon, Jan 9, 2023 at 9:21 PM Yann Sionneau <ysionneau@...ray.eu> wrote:
>> Hi Jeff,
>>
>> On 1/7/23 07:25, Jeff Xie wrote:
>>> Hi,
>>>
>>> On Wed, Jan 4, 2023 at 1:01 AM Yann Sionneau <ysionneau@...ray.eu> wrote:
>>>> [snip]
>>>>
>>>> A kvx toolchain can be built using:
>>>> # install dependencies: texinfo bison flex libgmp-dev libmpc-dev libmpfr-dev
>>>> $ git clone https://github.com/kalray/build-scripts
>>>> $ cd build-scripts
>>>> $ source last.refs
>>>> $ ./build-kvx-xgcc.sh output
>>> I would like to build the kvx-xgcc to compile and test the linux
>>> kernel, but it reported a compile error.
>>> I wonder what version of gcc you are using.
>>>
>>> My build environment:
>>> VERSION="20.04.2 LTS (Focal Fossa)"
>>> gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
>>>
>>>
>>> Compile error:
>>> $ ./build-kvx-xgcc.sh output
>>>
>>> ../../binutils/libiberty/fibheap.c: In function ‘fibheap_replace_key_data’:
>>> ../../binutils/libiberty/fibheap.c:38:24: error: ‘LONG_MIN’ undeclared
>>> (first use in this function)
>>> 38 | #define FIBHEAPKEY_MIN LONG_MIN
>>> | ^~~~~~~~
>>> [snip]
>> What SHA1 of https://github.com/kalray/build-scripts are you using?
> I have executed the "source last.refs"
I was referring to the SHA1 of the repo itself (build-scripts).
`last.refs` is a symbolic link which can point to several releases,
depending on "when" you did the clone.
I am asking this because we recently published new toolchains.
I want to make sure which one you are trying to build.
>> We are building our toolchain on Ubuntu 18.04 / 20.04 and 22.04 without
>> issues, I don't understand why it does not work for you, although indeed
>> the error log you are having pops out on my search engine and seems to
>> be some well known issue.
> Yes, there are many answers on the web, but none of them solve this problem.
>
>> If the build-script does not work for you, you can still use the
>> pre-built toolchains generated by the GitHub automated actions:
>> https://github.com/kalray/build-scripts/releases/tag/v4.11.1 ("latest"
>> means 22.04)
> Thanks, this is the final solution ;-)
Good to see it helped :)
Regards,
--
Yann
Powered by blists - more mailing lists