Arch Linux User Repository

@Angelsoul I just did a clean build ok, so it might be something on your machine. It kind of looks like you have an old version of Rust installed. If you have rustup, try running rustup update stable to update the Rust compiler before trying to build fnm.

@wezm Hi, Thanks for maintaining this package. I always installed fnm through their scripts, however I thought it was cleaner and more maintainable to take track of this package in pacman(AUR) as a system package.

I tried the installation but I am getting this error:

warning: unused manifest key: package.edition
error: failed to parse lock file at: /home/angelsoul/.cache/yay/fnm/src/fnm-1.38.1/Cargo.lock

Caused by:
  invalid serialized PackageId for key `package.dependencies`
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: fnm-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
fnm - exit status 4

I am not sure if this error is related to this AUR package or if it's a problem of the cargo package itself. I Just wanted to let you know, please ignore this comment if it is not related to the AUR package as I am currently using fnm-bin right now. Thanks.

@swsnr thanks for the input, applied the change.

Instead of "options=(!lto)" you can adapt CFLAGS in build via CFLAGS+=' -ffat-lto-objects', see https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/issues/20#note_171807

With this change it builds with LTO on OBS, see https://build.opensuse.org/package/show/home:swsnr:3rdparty/fnm

Thanks for the info and patch phnx47. I've removed provides("nodejs") and applied your patch.

One more, I think that better to remove provides("nodejs"), there are some side effects: https://aur.archlinux.org/packages/fnm-bin#comment-877207. I checked nvm, they are not provide nodejs. It is not affect me, but might someone else.

@wezm I checked with disabled LTO, can compile. Patch here: https://gist.github.com/phnx47/9ebad182d945775c9f59d236213b6a66

@wezm Hey! Did you have chance to check it in clean chroot? I checked today and it is still issue with ring:

          ring.18374ee3-cgu.0:(.text._ZN4ring10arithmetic6bigint11Nonnegative7to_elem17h8aa972c860465aedE+0x2a): undefined reference to `LIMBS_less_than'
          /usr/bin/ld: /build/fnm/src/fnm-1.31.1/target/release/deps/fnm-15f49a5d02bc0aff: hidden symbol `GFp_ia32cap_P' isn't defined
          /usr/bin/ld: final link failed: bad value
          collect2: error: ld returned 1 exit status

  = help: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)

error: could not compile `fnm` due to previous error

Indeed the issue looks familiar. Thanks for taking a look, but you don't need to as far as I'm concerned :) I'm now using the fnm-bin PKGBUILD, so I'm in no hurry for a fix here 😊 and I can also take a look at this myself some day😊

@lunaryorn I don't think it's a missing dependency but happy to proven wrong. I think it might be this issue: https://github.com/briansmith/ring/issues/1444 I haven't worked out why it doesn't happen for me yet. I can build it with paru. I'm currently travelling so don't have time to dig into this properly. I should be able to look into it more when I'm back home next week.