Jump to content

Search the Community

Showing results for tags 'emerge error'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

  • danielv's Blog
  • eusanpe
  • saraedward's Blog
  • Simple Step-by-Step Server Setup
  • andreawilson's Blog
  • maldoror's Blog
  • Not So Stupid Admin Tricks
  • drobbins' Blog
  • Sandro's Blog
  • Chris Kurlinski's Blog
  • decision theory
  • 666threesixes666's Blog
  • psychopatch's Blog
  • haxmeister's Blog
  • It's a Bear's life
  • Linux Container Club - LXD/LXC's Blog
  • Funtoo Perl Hackers's Perl on Funtoo

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


web


First Name


Last Name


Location


Interests

Found 2 results

  1. hi, i tried compiling rust on my desktop but it failed numerous time, i tried running emerge like i'd normally do, i also tried running it with only one job using MAKEOPTS="-j1", i have 12GiB of RAM and the same amount of swap so memory isn't the problem. i used these use flags : "clippy parallel-compiler rustfmt nightly" and here is the error (i also provided the output of emerge --info '=dev-lang/rust-1.46.0::lang-kit' as an attachment) anybody has any idea about what is causing this ? PS : i asked this question on the discord server too, please don't kill me if i shouldn't do it here too Running `/var/tmp/portage/dev-lang/rust-1.46.0/work/rust-stage0/bin/rustc --crate-name build_script_build /var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/vendor/crossbeam-utils/build.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -Cembed-bitcode=no -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="lazy_static"' --cfg 'feature="std"' -C metadata=b75193f5c76106f2 -C extra-filename=-b75193f5c76106f2 --out-dir /var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/build/bootstrap/debug/build/crossbeam-utils-b75193f5c76106f2 -L dependency=/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/build/bootstrap/debug/deps --extern autocfg=/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/build/bootstrap/debug/deps/libautocfg-ac8e1a092cbfaee6.rlib --cap-lints allow -C target-cpu=haswell -Cdebuginfo=2 -C linker=x86_64-pc-linux-gnu-gcc -Wrust_2018_idioms -Wunused_lifetimes -Dwarnings` The futex facility returned an unexpected error code. error: could not compile `memchr`. Caused by: process didn't exit successfully: `/var/tmp/portage/dev-lang/rust-1.46.0/work/rust-stage0/bin/rustc --crate-name memchr /var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/vendor/memchr/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -Cembed-bitcode=no -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="std"' --cfg 'feature="use_std"' -C metadata=bb39e2a5397cb723 -C extra-filename=-bb39e2a5397cb723 --out-dir /var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/build/bootstrap/debug/deps -L dependency=/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/build/bootstrap/debug/deps --cap-lints allow -C target-cpu=haswell -Cdebuginfo=2 -C linker=x86_64-pc-linux-gnu-gcc -Wrust_2018_idioms -Wunused_lifetimes -Dwarnings --cfg memchr_runtime_simd --cfg memchr_runtime_sse2 --cfg memchr_runtime_sse42 --cfg memchr_runtime_avx` (exit code: 134) warning: build failed, waiting for other jobs to finish... error: build failed Traceback (most recent call last): File "./x.py", line 11, in <module> bootstrap.main() File "/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 981, in main bootstrap(help_triggered) File "/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 948, in bootstrap build.build_bootstrap() File "/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 733, in build_bootstrap run(args, env=env, verbose=self.verbose) File "/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/src/bootstrap/bootstrap.py", line 143, in run raise RuntimeError(err) RuntimeError: failed to run: /var/tmp/portage/dev-lang/rust-1.46.0/work/rust-stage0/bin/cargo build --manifest-path /var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src/src/bootstrap/Cargo.toml --verbose --locked --frozen * ERROR: dev-lang/rust-1.46.0::lang-kit failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 3652: Called die * The specific snippet of code: * env $(cat "${S}"/config.env) RUST_BACKTRACE=1 "${EPYTHON}" ./x.py build -vv --config="${S}"/config.toml -j$(makeopts_jobs) || die * * If you need support, post the output of `emerge --info '=dev-lang/rust-1.46.0::lang-kit'`, * the complete build log and the output of `emerge -pqv '=dev-lang/rust-1.46.0::lang-kit'`. * The complete build log is located at '/var/tmp/portage/dev-lang/rust-1.46.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/rust-1.46.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src' * S: '/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src' * Messages for package dev-lang/rust-1.46.0: * ERROR: dev-lang/rust-1.46.0::lang-kit failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 3652: Called die * The specific snippet of code: * env $(cat "${S}"/config.env) RUST_BACKTRACE=1 "${EPYTHON}" ./x.py build -vv --config="${S}"/config.toml -j$(makeopts_jobs) || die * * If you need support, post the output of `emerge --info '=dev-lang/rust-1.46.0::lang-kit'`, * the complete build log and the output of `emerge -pqv '=dev-lang/rust-1.46.0::lang-kit'`. * The complete build log is located at '/var/tmp/portage/dev-lang/rust-1.46.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/rust-1.46.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src' * S: '/var/tmp/portage/dev-lang/rust-1.46.0/work/rustc-1.46.0-src' emerge-info
  2. Hello, hope everyone is going to have a good holiday. Is there anyone around who might be willing to offer a little help? Trying to update from 1.3 to 1.4. but getting lots of slot conflicts on the emerge world. Now I know this is probably not the way this is supposed to be done, but trying to emerge -u mesa will error out when trying to emerge libglvnd from github. Basically the error is: Fetching https://github.com/NVIDIA/libglvnd.git ... git fetch https://github.com/NVIDIA/libglvnd.git +HEAD:refs/git-r3/HEAD fatal: unable to access 'https://github.com/NVIDIA/libglvnd.git/': Couldn't resolve host 'github.com' * ERROR: media-libs/libglvnd-1.1.1.20190313-r1::core-gl-kit failed (unpack phase): * Unable to fetch from any of EGIT_REPO_URI See the build.log and libglvnd.info file, but I suspect that someone here knows precisely what's causing this outside of me trying to be smarter than: emerge -auDN @world --jobs=3 --exclude dev-lang/perl which results in a tons of slot conflict errors. So I am attempting to deal with this sequentially one pkg at a time manually. I really really should probably address the slot conflict errors on the emerge @world instead of diving down this wabbit hole, but I'm not so sure that if I did get the emerge @world to start emerging that I wouldn't get the libglvnd error anyway. Funtoo has always so stable that I just don't really mess with it other than to update occasionally and have been using it professionally for quite a number of years. So I've not found it really necessary to know all the tricks with portage and emerge until now. This is the first time I have ever tried to upgrade a live system to a new version , I've always installed on a live system in a chrooted environment. So instructions on https://www.funtoo.org/Upgrade_Instructions/1.4-release are not working so good for me. Probably nutz to keep on doing this, I should just abort and install 1.4 to a chrooted environment instead of going through all this pain, but now I'm kind of committed to this path and I'd really like to know what's up with that git fetch error on the libglvnd package. Anyone? Thanks in advance, Nikki libglvnd.info build.log
×
×
  • Create New...