Re: [RFC PATCH 00/25] Upstream kvx Linux port

From: Yann Sionneau
Date: Mon Jan 09 2023 - 10:32:10 EST


Hi Jeff,

On 1/9/23 16:11, Jeff Xie wrote:
On Mon, Jan 9, 2023 at 9:21 PM Yann Sionneau <ysionneau@xxxxxxxxx> 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@xxxxxxxxx> 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