error: ‘scm_new_port_table_entry’ was not declared in this scope about riscv-binutils-gdb HOT 9 CLOSED

This isn't a problem in binutils; rather, it is a Guile library version mismatch. See riscv-collab/riscv-gnu-toolchain#244 and riscv-collab/riscv-gnu-toolchain#247

from riscv-binutils-gdb.

Specifically the workaround with riscv-collab/riscv-gnu-toolchain#247 would be to either install a compatible Guile version and specify that, or specify --with-guile=no, when building riscv-gnu-toolchain.

from riscv-binutils-gdb.

@kyrias Strange, I do not understand why is your pull request not merged.

I have tried with ./build.sh --with-guile=no , I suppose this is not the correct way to do so.

Do I need to nodify the 3 files in riscv-gnu-toolchain on my own ?

from riscv-binutils-gdb.

@kyrias sorry for multiple posting of comments. I am now using the merged commit and the error still persists. I have tried building toolchain with and without using autoreconf, I have no idea what I have missed out. Do you have any idea ?

from riscv-binutils-gdb.

Add --with-guile=no to the riscv-gnu-toolchain line in build.sh.

from riscv-binutils-gdb.

adding that to build.sh also does not work.
My system guile version is guile (GNU Guile) 2.2.2

build_project riscv-gnu-toolchain --prefix=$RISCV --with-guile=no

build.txt

from riscv-binutils-gdb.

Are you entirely certain that the riscv-gnu-toolchain submodule is in fact the one with it? And what exactly does the build.sh line look like now?

from riscv-binutils-gdb.

@ProMach Could you try running git -C riscv-gnu-toolchain describe --long --tags from the riscv-tools directory?

from riscv-binutils-gdb.

@kyrias Thanks. It is solved.

from riscv-binutils-gdb.