Setup RISCV-GCC compiler toolchain "ERROR"

[Ahmed Juba]

Hello everyone, 
I'm trying to setting up the gcc compiler toolchain on CentOS, but there's some error keeps showing up, i tried alot to solve it but i could't

```
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc: In function ‘std::string same_ratio_eew_type(unsigned int, int, unsigned int, bool, bool)’:
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:118:30: error: ‘log2’ is not a member of ‘std’
     elmul_log2 = lmul_log2 - std::log2 (sew / eew);
                              ^
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:118:30: note: suggested alternative:
In file included from /usr/include/features.h:375:0,
                 from /usr/include/stdio.h:27,
                 from ../../../gcc/gcc/system.h:46,
                 from ../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:18:
/usr/include/bits/mathcalls.h:145:1: note:   ‘log2’
 __MATHCALL (log2,, (_Mdouble_ __x));
 ^
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:120:30: error: ‘log2’ is not a member of ‘std’
     elmul_log2 = lmul_log2 + std::log2 (eew / sew);
                              ^
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:120:30: note: suggested alternative:
In file included from /usr/include/features.h:375:0,
                 from /usr/include/stdio.h:27,
                 from ../../../gcc/gcc/system.h:46,
                 from ../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:18:
/usr/include/bits/mathcalls.h:145:1: note:   ‘log2’
 __MATHCALL (log2,, (_Mdouble_ __x));
 ^
make[2]: *** [build/genrvv-type-indexer.o] Error 1
make[2]: Leaving directory `/home/ICer/CHIPSAlliance/riscv-dv/gcc-demo/build/build-gcc-newlib-stage1/gcc'
make[1]: *** [all-gcc] Error 2
make[1]: Leaving directory `/home/ICer/CHIPSAlliance/riscv-dv/gcc-demo/build/build-gcc-newlib-stage1'
make: *** [stamps/build-gcc-newlib-stage1] Error 2
[ICer@IC_EDA /home/ICer/CHIPSAlliance/riscv-dv/gcc-demo/build]$
```

[Tommy Murphy]

Same issue as mentioned here perhaps?

* https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/OGAtlT4zVPg

[Ahmed Juba]

Yes, i think so but it's a different situation.
I was trying to setup RISC-V GNU Compiler Toolchain from here:  riscv-collab/riscv-gnu-toolchain: GNU toolchain for RISC-V, including GCC (github.com)

by the following commands:
```
  git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git gcc-demo
     sudo yum install autoconf automake python3 libmpc-devel mpfr-devel gmp-devel \ gawk bison flex texinfo patchutils gcc gcc-c++ zlib-devel expat-devel
  cd gcc-demo/ mkdir build cd build/  
  ../configure --prefix=/home/ICer/riscv-demo export PATH="$HOME/riscv-demo/bin:$PATH"
sudo make    
```
this error shows up after sudo make, and ` riscv64-unknown-elf-gcc` isn't installed due to the errors.
So exactly, what should i do?

[Tommy Murphy]

I'm pretty sure that this works fine for me - at least on WSL2/Ubuntu 20.04.

I'm just trying again now to check.

What CentOS version are you using?

What is your build log (e.g. `make 2>&1 | tee build.log`)?

[Christoph Müllner]

On Mon, Feb 5, 2024 at 10:38 AM Ahmed Juba <ahmed.j...@gmail.com> wrote:
>
> Yes, i think so but it's a different situation.
> I was trying to setup RISC-V GNU Compiler Toolchain from here: riscv-collab/riscv-gnu-toolchain: GNU toolchain for RISC-V, including GCC (github.com)
>
> by the following commands:
> ```
> git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git gcc-demo
> sudo yum install autoconf automake python3 libmpc-devel mpfr-devel gmp-devel \ gawk bison flex texinfo patchutils gcc gcc-c++ zlib-devel expat-devel
> cd gcc-demo/ mkdir build cd build/
> ../configure --prefix=/home/ICer/riscv-demo export PATH="$HOME/riscv-demo/bin:$PATH"
> sudo make

Independent of the actual issue: please, never use "sudo make".
Only install into directories where you have the necessary permissions
(ensure this before calling make).

I'm not sure if out of tree builds (mkdir build; cd build;
../configure) work with that repository.
So, instead of out of tree building, I suggest using git worktree (if
multiple builds are needed) and
in-tree builds.

Also note that " cd gcc-demo/ mkdir build cd build/ " (copied from
your instruction list) will not even enter the directory gcc-demo,
because you are missing semicolons (';') between the commands.
Given your build started, it seems you did not put the instructions in
the email that were actually used to build the toolchain.

Further, I don't understand why you are setting PATH.

BR
Christoph

> ```

> this error shows up after sudo make, and ` riscv64-unknown-elf-gcc` isn't installed due to the errors.
> So exactly, what should i do?
>
> On Monday, February 5, 2024 at 11:13:32 AM UTC+2 tommy_...@hotmail.com wrote:
>>
>> Same issue as mentioned here perhaps?
>>
>> * https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/OGAtlT4zVPg
>

> --
> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/23f4385d-c181-4a0f-81e6-cd132479e717n%40groups.riscv.org.

[Tommy Murphy]

On Monday 5 February 2024 at 09:51:05 UTC christoph...@vrull.eu wrote:

Independent of the actual issue: please, never use "sudo make".
Only install into directories where you have the necessary permissions
(ensure this before calling make).

This keeps cropping up because the default install location is `/opt/riscv` and this leads people to think that they need `sudo`.

Well, they generally do if they leave don't override the default install location of `/opt/riscv` using `configure --prefix=...`.

But some keep doing it even when they're using a "local" directory.

* https://github.com/riscv-collab/riscv-gnu-toolchain?tab=readme-ov-file#installation-newlib

 

I'm not sure if out of tree builds (mkdir build; cd build;
../configure) work with that repository.
So, instead of out of tree building, I suggest using git worktree (if
multiple builds are needed) and
in-tree builds.

I'm a bit confused - I don't see any out of tree building above.

Where do you see it?

* https://github.com/riscv-collab/riscv-gnu-toolchain?tab=readme-ov-file#use-source-tree-other-than-riscv-gnu-toolchain

 

Also note that " cd gcc-demo/ mkdir build cd build/ " (copied from
your instruction list) will not even enter the directory gcc-demo,
because you are missing semicolons (';') between the commands.

I assumed that these were copy/paste errors and line breaks were lost?

 

Given your build started, it seems you did not put the instructions in
the email that were actually used to build the toolchain.

Agreed.

 

Further, I don't understand why you are setting PATH.

Me neither.

[Christoph Müllner]

On Mon, Feb 5, 2024 at 10:59 AM Tommy Murphy <tommy_...@hotmail.com> wrote:
>
>
>
> On Monday 5 February 2024 at 09:51:05 UTC christoph...@vrull.eu wrote:
>
> Independent of the actual issue: please, never use "sudo make".
> Only install into directories where you have the necessary permissions
> (ensure this before calling make).
>
>
> This keeps cropping up because the default install location is `/opt/riscv` and this leads people to think that they need `sudo`.
> Well, they generally do if they leave don't override the default install location of `/opt/riscv` using `configure --prefix=...`.
> But some keep doing it even when they're using a "local" directory.
>
> * https://github.com/riscv-collab/riscv-gnu-toolchain?tab=readme-ov-file#installation-newlib
>
>
> I'm not sure if out of tree builds (mkdir build; cd build;
> ../configure) work with that repository.
> So, instead of out of tree building, I suggest using git worktree (if
> multiple builds are needed) and
> in-tree builds.
>
>
> I'm a bit confused - I don't see any out of tree building above.
> Where do you see it?
>
> * https://github.com/riscv-collab/riscv-gnu-toolchain?tab=readme-ov-file#use-source-tree-other-than-riscv-gnu-toolchain

We are talking about different things:
* sources of toolchain components (GCC, QEMU, etc) are out of tree
-> we override the sources to some local path (documented in the
link that you have provided)
* building riscv-gnu-toolchain out of tree itself in an empty build directory

Ahmed stated that he did the following:

git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git gcc-demo

cd gcc-demo/
mkdir build
cd build/

../configure --prefix=/home/ICer/riscv-demo export
PATH="$HOME/riscv-demo/bin:$PATH"

So he creates a build directory and from there executes "../configure
... ; make ...".
Since the source directory of riscv-gnu-toolchain and the build
directory are different he does an out of tree build of the
riscv-gnu-toolchain repo.

>
>
> Also note that " cd gcc-demo/ mkdir build cd build/ " (copied from
> your instruction list) will not even enter the directory gcc-demo,
> because you are missing semicolons (';') between the commands.
>
>
> I assumed that these were copy/paste errors and line breaks were lost?

Possible, but I don't want to guess/assume.
If so, then it was an out-of-tree build and likely the source of the
build error.

[Tommy Murphy]

On Monday 5 February 2024 at 10:11:29 UTC christoph...@vrull.eu wrote:

We are talking about different things:
* sources of toolchain components (GCC, QEMU, etc) are out of tree
-> we override the sources to some local path (documented in the
link that you have provided)
* building riscv-gnu-toolchain out of tree itself in an empty build directory

Ahmed stated that he did the following:
git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git gcc-demo
cd gcc-demo/
mkdir build
cd build/
../configure --prefix=/home/ICer/riscv-demo export
PATH="$HOME/riscv-demo/bin:$PATH"

So he creates a build directory and from there executes "../configure
... ; make ...".
Since the source directory of riscv-gnu-toolchain and the build
directory are different he does an out of tree build of the
riscv-gnu-toolchain repo.

Ah - OK - I understand what you're referring to now.

I've done builds like that recently (a few weeks ago) and they worked fine.

E.g.

```

git clone  https://github.com/riscv-collab/riscv-gnu-toolchain.git test

cd test

mkdir mybuilddir

cd mybuilddir

../configure ...

make

```

I normally just build in the root directory of the cloned repo though.

[Christoph Müllner]

Ok, I never did this before.
Good to know this actually works.

[Tommy Murphy]

I'm just double checking such a build on WSL2/Ubuntu 20.04 to be sure.

I'm pretty sure it'll work.

Ahmed should maybe clarify what version of CentOS is being used and provide the build log for a clean build. E.g.

```

make distclean

rm -rf /home/ICer/riscv-demo

make 2>&1 | tee build.log

```

I've never done builds on CentOS so maybe there's something odd there?

[Ahmed Juba]

CentOS Linux release 7.9.2009 (Core)

[Tommy Murphy]

Can you modify your build commands to omit the `export PATH="$HOME/riscv-demo/bin:$PATH"` and see if that makes any difference?

Just in case having the toolchain that you're trying to build on the PATH at build time causes problems?

Basically:

```

git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git gcc-demo

cd gcc-demo/

mkdir build

cd build/  
../configure --prefix=/home/ICer/riscv-demo

make distclean

rm -rf /home/ICer/riscv-demo

```

[Tommy Murphy]

FWIW I did a test build on my WSL2/Ubuntu 20.04 machine as follows and it worked fine.

```

cd ~/Downloads

git clone https://github.com/riscv-collab/riscv-gnu-toolchain mailing-list

cd mailing-list

mkdir mybuild

cd mybuild

../configure --prefix=`pwd`/installed-tools

make 2>&1 | tee build.log

```

Compressed `build.log` attached.

[Tommy Murphy]

I also tried this:

```

../configure --prefix=$HOME/Downloads/mailing-list/installed-tools export PATH=$HOME/Downloads/mailing-list/installed-tools/bin:$PATH

```

but got lots of wanings:

```

configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/dotnet/:/mnt/c/Program
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/Meld/:/mnt/c/Program
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/nodejs/:/mnt/c/Program
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/Git/cmd:/mnt/c/Program
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/Crucial/Crucial
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Executive:/mnt/c/Program
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/PuTTY/:/mnt/c/Program
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Files/usbipd-win/:/mnt/c/Users/Tommy
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Murphy/scoop/shims:/mnt/c/Users/Tommy
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Murphy/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/Tommy
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Murphy/AppData/Roaming/npm:/mnt/c/Users/Tommy
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Murphy/AppData/Local/Programs/Microsoft
configure: WARNING: you should use --build, --host, --target
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: Code/bin:/snap/bin
checking for export-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for fgrep... /usr/bin/grep -F
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for bash... /bin/bash
checking for __gmpz_init in -lgmp... yes
checking for mpfr_init in -lmpfr... yes
checking for mpc_init2 in -lmpc... yes
checking for curl... /usr/bin/curl
checking for wget... /usr/bin/wget
checking for ftp... /usr/bin/ftp
configure: creating ./config.status
config.status: creating Makefile
config.status: creating scripts/wrapper/awk/awk
config.status: creating scripts/wrapper/sed/sed

```

Do you get those or should the commands actually executed separately?

```

../configure --prefix=$HOME/Downloads/mailing-list/installed-tools

export PATH=$HOME/Downloads/mailing-list/installed-tools/bin:$PATH

make

```

[Ahmed Juba]

Thanks alot for trying to help me, but still the same errors :(

[Tommy Murphy]

I will try a test build on a CentOS 7 VM but at this stage I think that you should probably consider trying a clean (virtual or physical) machine installation to eliminate the possibility of something on your work machine causing problems.

[Ahmed Juba]

thank you for trying harder. 
can you provide me with the commands to do so?

[Tommy Murphy]

> can you provide me with the commands to do so?

I don't understand - to do what?

If you mean how to install a VM then you'll need to research that yourself.

I generally use VirtualBox or WSL2.

Both are fairly simple to use to get a VM up and running.

[Ahmed Juba]

oh my bad, i misunderstood you. i will use another VM which's:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy

[Tommy Murphy]

Ok - I can reproduce the problem on a VirtualBox VM installation of CentOS 7.9 2009.

The build fails with the same errors:

```

g++ -std=gnu++11 -c   -g -O2   -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE   -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H  -DGENERATOR_FILE -I. -Ibuild -I../../../gcc/gcc -I../../../gcc/gcc/build -I../../../gcc/gcc/../include  -I../../../gcc/gcc/../libcpp/include  \
-o build/genrvv-type-indexer.o ../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc

../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc: In function ‘std::string same_ratio_eew_type(unsigned int, int, unsigned int, bool, bool)’:
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:118:30: error: ‘log2’ is not a member of ‘std’
     elmul_log2 = lmul_log2 - std::log2 (sew / eew);
                              ^
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:118:30: note: suggested alternative:
In file included from /usr/include/features.h:375:0,
                 from /usr/include/stdio.h:27,
                 from ../../../gcc/gcc/system.h:46,
                 from ../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:18:
/usr/include/bits/mathcalls.h:145:1: note:   ‘log2’
 __MATHCALL (log2,, (_Mdouble_ __x));
 ^
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:120:30: error: ‘log2’ is not a member of ‘std’
     elmul_log2 = lmul_log2 + std::log2 (eew / sew);
                              ^
../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:120:30: note: suggested alternative:
In file included from /usr/include/features.h:375:0,
                 from /usr/include/stdio.h:27,
                 from ../../../gcc/gcc/system.h:46,
                 from ../../../gcc/gcc/config/riscv/genrvv-type-indexer.cc:18:
/usr/include/bits/mathcalls.h:145:1: note:   ‘log2’
 __MATHCALL (log2,, (_Mdouble_ __x));
 ^
make[2]: *** [build/genrvv-type-indexer.o] Error 1

make[2]: Leaving directory `/home/user/Downloads/riscv-gnu-toolchain/build/build-gcc-newlib-stage1/gcc'

make[1]: *** [all-gcc] Error 2

make[1]: Leaving directory `/home/user/Downloads/riscv-gnu-toolchain/build/build-gcc-newlib-stage1'

make: *** [stamps/build-gcc-newlib-stage1] Error 2

```

The default GCC installed on CentOS 7 is 4.8.5 which is quite old:

```

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC)

``` 

I wonder if that's too old to build the toolchain these days?

Let's try a later one (the latest that I can find at a glance is GCC 11):

```

# https://forums.centos.org/viewtopic.php?t=71219

sudo yum install centos-release-scl-rh
sudo yum install devtoolset-11-toolchain
scl enable devtoolset-11 bash

gcc -v

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,lto --prefix=/opt/rh/devtoolset-11/root/usr --mandir=/opt/rh/devtoolset-11/root/usr/share/man --infodir=/opt/rh/devtoolset-11/root/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-gcc-major-version-only --with-linker-hash-style=gnu --with-default-libstdcxx-abi=gcc4-compatible --enable-plugin --enable-initfini-array --with-isl=/builddir/build/BUILD/gcc-11.2.1-20220127/obj-x86_64-redhat-linux/isl-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.2.1 20220127 (Red Hat 11.2.1-9) (GCC)

 
cd ~/Downloads/riscv-gnu-toolchain
rm -rf build
mkdir build
cd build

../configure --prefix=`pwd`/installed-tools
make 2>&1 | tee build.log

```

I'll post back with results ASAP.

[Tommy Murphy]

Quick update - CentOS 7.9 2009 build using GCC 11 (via devtoolset-11-toolchain) completed successfully.

I guess that GCC 4.8.5 is simply too old to build the toolchain these days?

I'm not sure what the minimum GCC version might be.

[Ahmed Juba]

Thank you for the great effort, really appreciate it.

Does this GCC 11 toolchain will be suitable for RISC-V DV by CHIPS Alliance?

--
You received this message because you are subscribed to a topic in the Google Groups "RISC-V SW Dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/groups.riscv.org/d/topic/sw-dev/GJALfwNgtbI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sw-dev+un...@groups.riscv.org.
To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/d4185ab7-ab46-4024-9552-97c920843165n%40groups.riscv.org.

[Tommy Murphy]

On Monday 5 February 2024 at 16:59:02 UTC ahmed.j...@gmail.com wrote:

Thank you for the great effort, really appreciate it.

You're welcome.

 

Does this GCC 11 toolchain will be suitable for RISC-V DV by CHIPS Alliance?

Just to clarify - I used GCC 11 on CentOS 7 to build the GCC 13.2 RISC-V toolchain - i.e. a RISC-V cross compiler toolchain that runs on Linux x86_64.

So the RISC-V GCC is 13.2 not 11.

I would expect that this is fine but can't say for sure as I know nothing about  CHIPS Alliance RISC-V DV.

I would expect that this sort of application just needs a working toolchain and how it's built doesn't really matter (as long as it has been built successfully obviously).

Maybe ask over at the RISC-V DV community?

Maybe they have more specific guidelines for how to build the RISC-V toolchain and other relevant tools?