Package Details: juliaup 1.14.5-3

Git Clone URL: https://aur.archlinux.org/juliaup.git (read-only, click to copy)
Package Base: juliaup
Description: An experimental Julia version manager
Upstream URL: https://github.com/JuliaLang/juliaup
Licenses: MIT
Conflicts: julia, julia-bin
Provides: julia
Submitter: simeonschaub
Maintainer: simeonschaub (juliaupbot, giordano, vchuravy, Moelf)
Last Packager: simeonschaub
Votes: 7
Popularity: 0.199264
First Submitted: 2021-08-11 10:33 (UTC)
Last Updated: 2024-02-21 18:02 (UTC)

Dependencies (1)

Required by (20)

Sources (1)

Latest Comments

Sarjo commented on 2024-02-16 18:25 (UTC)

Further consulting the ring bug (https://github.com/briansmith/ring/issues/1444) discussion suggests it is specific to GCC's LTO. Based on one of the comments in the github thread, I was able to build successfully by using clang instead of GCC. This was done by replacing the PKGBUILD line

cargo build --release --bin juliaup --bin julialauncher --features binjulialauncher --target-dir ./target

by

RUSTFLAGS="-Clinker=clang-16 -Clink-arg=-fuse-ld=lld -Clinker-plugin-lto" RUSTDOCFLAGS=$RUSTFLAGS CC=clang-16 AR=llvm-ar CFLAGS=-flto=auto cargo build --release --bin juliaup --bin julialauncher --features binjulialauncher --target-dir ./target

gtsiam commented on 2024-02-16 07:30 (UTC)

See this bug: https://github.com/briansmith/ring/issues/1444

I'm not sure what exactly causes this, given that lto has been on by default for a while now. But for the time being, I've been able to build by patching with options=(!lto).

togo59 commented on 2024-02-15 17:13 (UTC)

FWIW, The first line of the error list is error: linking withccfailed: exit status: 1 | = note: LC_ALL="C" PATH="/usr/lib64/rustlib/x86_64-unknown-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl" VSLANG="1033" "cc" "-m64" "/tmp/rustcXOPu5A/symbols.o" "/home/roger/.cache/yay/juliaup/src/juliaup-1.14.5/./target/release/deps/juliaup-75493d37f3ad7980.juliaup.5ba0f7400c9596f3-cgu.0.rcgu.o" "-Wl,--as-needed" "-L" "/home/roger/.cache/yay/juliaup/src/juliaup-1.14.5/./target/release/deps" "-L" "/home/roger/.cache/yay/juliaup/src/juliaup-1.14.5/./target/release/build/ring-efd597de85992b45/out" "-L" "/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "/tmp/rustcXOPu5A/libring-39edb496e356d38c.rlib" "/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-dc359f8c64813cd3.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-z,noexecstack" "-L" "/usr/lib64/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/home/roger/.cache/yay/juliaup/src/juliaup-1.14.5/./target/release/deps/juliaup-75493d37f3ad7980" "-Wl,--gc-sections" "-pie" "-Wl,-z,relro,-z,now" "-Wl,-O1" "-nodefaultlibs"

Moelf commented on 2024-02-14 14:25 (UTC)

also hitting linking error now

mnussbaum commented on 2024-02-14 08:58 (UTC)

I'm seeing an error during the linking stage of installation:

 /usr/bin/ld: /tmp/rustcpRjCdx/libring-96a9c51e84cfd22a.rlib(97d78e7428c2dbc0-x86_64-mont5-elf.o):/home/mnussbaum/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ring-0.17.7/pregenerated/x86_64-mont5-elf.S:2
4: more undefined references to `ring_core_0_17_7_OPENSSL_ia32cap_P' follow

BoostCookie commented on 2024-02-03 09:54 (UTC)

@simeonschaub juliaup now has the completions command, just like rustup. Could you please add the completions to the PKGBUILD? Just copy the relevant lines from the rustup PKGBUILD: https://gitlab.archlinux.org/archlinux/packaging/packages/rustup/-/blob/main/PKGBUILD?ref_type=heads

daylily commented on 2023-12-14 12:53 (UTC)

Building the latest version prints the following error:

$ makepkg -is
==> Making package: juliaup 1.12.5-2 (Thu Dec 14 08:48:26 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found v1.12.5.tar.gz
==> Validating source files with md5sums...
    v1.12.5.tar.gz ... Passed
==> Extracting sources...
  -> Extracting v1.12.5.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
warning: file `~/Downloads/juliaup/src/juliaup-1.12.5/src/bin/julialauncher.rs` found to be present in multiple build targets:
  * `bin` target `julia`
  * `bin` target `julialauncher`
error: failed to determine package fingerprint for build script for juliaup v1.12.5 (~/Downloads/juliaup/src/juliaup-1.12.5)

Caused by:
  failed to determine the most recently modified file in ~/Downloads/juliaup/src/juliaup-1.12.5

Caused by:
  failed to determine list of files in ~/Downloads/juliaup/src/juliaup-1.12.5

Caused by:
  failed to open git index at ~/Downloads/juliaup/.git/

Caused by:
  invalid data in index - calculated checksum does not match expected; class=Index (10)
==> ERROR: A failure occurred in build().
    Aborting...

Removing the .git directory makes the error go away. Not sure what is happening; maybe a bug with libgit2: https://github.com/libgit2/libgit2/issues/6531

simeonschaub commented on 2023-12-14 10:12 (UTC)

Should be fixed now

surname3046 commented on 2023-12-07 12:23 (UTC)

The installation of the package doesn't succeed when the user has specified a custom target dir in their global Cargo config.toml file. The following two commands then fail as the target directory doesn't exist.

  install -Dm755 "${srcdir}/$pkgname-$pkgver/target/release/juliaup" "${pkgdir}/usr/bin/juliaup"
  install -Dm755 "${srcdir}/$pkgname-$pkgver/target/release/julialauncher" "${pkgdir}/usr/bin/julialauncher"

This issue can be resolved by adding the --target-dir ./target flag to the cargo build invocation.