Package Details: rustpython-git r11862.2a26ed009-1

Git Clone URL: (read-only, click to copy)
Package Base: rustpython-git
Description: A Python3 Interpreter written in Rust
Upstream URL:
Licenses: MIT
Submitter: fordprefect
Maintainer: fordprefect
Last Packager: fordprefect
Votes: 3
Popularity: 0.000001
First Submitted: 2019-02-07 10:34 (UTC)
Last Updated: 2022-09-24 14:53 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

Neko-san commented on 2022-09-24 14:36 (UTC) (edited on 2022-09-24 14:36 (UTC) by Neko-san)

Ah, okay, so there's a couple reasons why:

1) The issue I mentioned was apparently because I have Clang set as the C/C++ compiler in makepkg.conf but messed up it's LD variable; I had it set to /usr/bin/ld.lld instead of /usr/bin/lld-link (which I never knew for the longest time)

2) Later in the check() function, it fails (if built in a chroot) because python itself isn't listed as a makedepend

fordprefect commented on 2022-09-24 13:45 (UTC)

@Neko-san: Can't reproduce with the rust compiler from the official repos. Consider using those and report back if it doesn't work.

Neko-san commented on 2022-09-21 22:26 (UTC)

I keep getting this error every time I try to compile; using rustc 1.66.0-nightly (432abd86f 2022-09-20):

. . .
warning: doesn't exist. regenerate.

error: failed to run custom build command for `rustpython-parser v0.1.2 (/mnt/extraStorage/AUR/rustpython-git/src/RustPython/compiler/parser)`

Caused by:
  process didn't exit successfully: `/mnt/extraStorage/AUR/rustpython-git/src/RustPython/target/release/build/rustpython-parser-acbe8425df4f499f/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=python.lalrpop doesn't exist. regenerate.

  --- stderr
  thread 'main' panicked at 'try: cargo build --manifest-path=compiler/parser/Cargo.toml --features=lalrpop', compiler/parser/
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

marc00077 commented on 2021-11-01 20:54 (UTC) (edited on 2021-11-01 20:54 (UTC) by marc00077)

@fordprefect: The problem was exactly what was pointed: I had rust version 1.44.1 (even though my system was fully updated). Replacing the package rustup for rust fixed the problem. Installing with yay yielded the following error: thread 'main' panicked at 'initialization failed; run with RUST_BACKTRACE=1 to see Python backtrace', vm/src/ but running the executable build with makepkg worked perfectly. This last error seems to be related to the RUSTPYTHONPATH envvar that makes the yay-generated binary to look for the Lib folder in the incorrect place /home/xxxxxx/.cache/yay/rustpython-git/src/RustPython/vm/pylib-crate/Lib

fordprefect commented on 2021-10-31 13:19 (UTC)

@marc00077: Sounds like an outdated rust/cargo, builds fine for me with rust-1:1.56.0. Also please don't report issues with wrappers (in your case yay), but always try with plain makepkg first.

marc00077 commented on 2021-10-30 18:23 (UTC)

Not building for me :( error: failed to parse manifest at /home/xxxxxx/.cache/yay/rustpython-git/src/RustPython/Cargo.toml

Caused by: failed to parse the edition key

Caused by: supported edition values are 2015 or 2018, but 2021 is unknown