Summary: | dev-util/cbindgen-0.25.0: build fail, failed to make network request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | darkstalker <slayerbeast> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
darkstalker
2023-10-04 18:30:07 UTC
Created attachment 872134 [details]
build log
Yeah we don't allow internet connection while building packages so the build system doesn't do anything we can't anticipate / we don't want to. I'm not a rust expert, but it looks like the build system can't quite detect your system rust right. 1: Are you cross-compiling? 2: What are your use flags for rust? 3: I could look at your pure make.conf, and any env/ files for rust or any rust-related package you might have added. I figured out the issue, it was on my end. So I used to run some extra configs under /etc/portage/profile so I could use my already installed Rust via rustup instead of compiling it: package.provided ``` dev-lang/rust-bin-1.71.1 ``` profile.bashrc ``` BASEDIR=/home/user VERSION=1.71.1 export PATH="$BASEDIR/.cargo/bin:$PATH" STABLE="$BASEDIR/.rustup/toolchains/$VERSION-x86_64-unknown-linux-gnu" rustup toolchain link build-stable "$STABLE" &> /dev/null rustup default build-stable &> /dev/null ``` I've ran this for years and it worked fine, until now. I decided to remove them and let portage compile it's own system Rust, and now the package compiled successfully. |