Skip to content

Building fails due to binutils cloning / branch issue #1700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
emeb opened this issue Apr 6, 2025 · 2 comments
Closed

Building fails due to binutils cloning / branch issue #1700

emeb opened this issue Apr 6, 2025 · 2 comments

Comments

@emeb
Copy link

emeb commented Apr 6, 2025

I'm trying to build newlib/multilib on Raspbian 64 with the following commands:

git clone https://github.com/riscv/riscv-gnu-toolchain
cd riscv-gnu-toolchain/
./configure --prefix=/opt/riscv-gcc/4-6-2025 --enable-multilib
make

It begins but after a few minutes I get the following result:

Cloning into '/home/ericb/Engineering/github/riscv-gnu-toolchain/binutils'...
remote: Enumerating objects: 40846, done.        
remote: Counting objects: 100% (40846/40846), done.        
remote: Compressing objects: 100% (31849/31849), done.        
remote: Total 40846 (delta 10609), reused 24462 (delta 7607), pack-reused 0        
Receiving objects: 100% (40846/40846), 78.21 MiB | 3.31 MiB/s, done.
Resolving deltas: 100% (10609/10609), done.
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
error: RPC failed; curl 16 Error in the HTTP2 framing layer
fatal: the remote end hung up unexpectedly
fatal: Fetched in submodule path 'binutils', but it did not contain beb2cdbcda911764b2bed5e57921fe90493260bd. Direct fetching of that commit failed.
make: *** [Makefile:348: /home/ericb/Engineering/github/riscv-gnu-toolchain/binutils/.git] Error 128

I've tried several times with the same error. Any thoughts what's going on?

@TommyMurphyTM1234
Copy link
Collaborator

Known issue:

Workaround here:

You'll have to do a clean clone for that to work:

@emeb
Copy link
Author

emeb commented Apr 6, 2025

Thanks, that appears to have resolved the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants