Arch Linux User Repository

git is missing in makedepends and is not in base-devel, so should be added, see VCS packages Arch Wiki page: https://wiki.archlinux.org/title/VCS_package_guidelines#Conflicts_and_dependencies Testing to build in a chroot with e.g. paru -S rustpython-git --chroot (does all the setup for chroot builds for you) shows issues like this nicely.

The commented out empty depends array could also be cleaned up in the PKGBUILD in case you're already changing something else (or replaced with some comment in case that signifies something).

@actionless: Thanks for the suggestions, implemented. For the future, please explain the changes instead of pasting a diff without rationale. I'd consider this pretty rude, actually.

to avoid problem with build flags:

@@ -9,6 +9,7 @@ makedepends=('rust' 'python')
 license=('MIT')
 source=('git+https://github.com/RustPython/RustPython.git')
 md5sums=('SKIP')
+options=('!buildflags' '!strip')

 pkgver() {
   cd RustPython

and to include all features:

@@ -17,13 +18,13 @@ pkgver() {

 build() {
     cd "$srcdir/RustPython"
-    cargo build --release --locked
+    cargo build --release --locked --features jit --features ssl
 }

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

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

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

. . .
warning: python.rs 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
  cargo:warning=python.rs doesn't exist. regenerate.

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

@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/vm.rs:384:14 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

@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.

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