Arch Linux User Repository

If anyone else would like to be added as maintainer, I'd be happy to do so.

Apologies for the delay, should be fixed now.

After debugging, I found that there was indeed a discrepancy in RUSTFLAGS. RUSTFLAGS was not set when building from source, but was getting RUSTFLAGS=-C force-frame-pointers=yes -C debuginfo=2 --remap-path-prefix=$HOME/surfer-waveform-git/src=/usr/src/debug/surfer-waveform-git when using makepkg. Exporting the RUSTFLAGS from the makepkg environment while building from source also results in OOM. Adding !debug to the options array in PKGBUILD fixes the OOM error. Any reason not to add !debug in the PKGBUILD?

Please try makepkg rather than paru. I can see https://github.com/Morganamilo/paru/issues/1383.

If that still fails I think you need to start dumping RUSTFLAGS and look for discrepancies. This will be hard for me to debug because it Works On My Machine^TM, but any additional information you can gather is greatly appreciated.

I am building surfer from source via the following commands.

export RUSTUP_TOOLCHAIN=stable
export CARGO_TARGET_DIR=target
export PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1
cargo build --frozen --release --all-features

These commands are also present in the build() function of the PKGBUILD. Building from source compiles successfully but installing via paru gets OOM killed. Following are the flags in my makepkg.conf.

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection \
        -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
         -Wl,-z,pack-relative-relocs"

LTOFLAGS won't matter due to options=(!lto) in PKGBUILD.

Also, https://gitlab.com/surfer-project/surfer/-/issues/424 was resolved so sed -i 's/#!\[deny(unused_crate_dependencies)\]//g' libsurfer/src/lib.rs can be removed now.

I am getting OOM errors when building surfer via paru.

In my experience the two main factors that determine memory usage during compilation are 1) number of parallel processes used 2) optimisation level (especially LTO).

Please double check that the compilation flags (e.g RUSTFLAGS) are the exact same both times; I suspect you'll find a discrepancy.

I am getting OOM errors when building surfer via paru. However, following the build steps defined in the PKGBUILD (exporting the environment variables and executing cargo build --release --frozen --all-features) and building surfer from a freshly cloned repository, it is successfully building and no OOM errors are being reported. What could be going wrong?

I am getting the following error.

Thanks, I've added a sed to workaround it and reported this upstream: https://gitlab.com/surfer-project/surfer/-/issues/424

I am getting the following error.

error: extern crate `serde_stacker` is unused in crate `libsurfer`
  |
  = help: remove the dependency or add `use serde_stacker as _;` to the crate root
note: the lint level is defined here
 --> libsurfer/src/lib.rs:1:9
  |
1 | #![deny(unused_crate_dependencies)]
  |         ^^^^^^^^^^^^^^^^^^^^^^^^^

warning: unused variable: `t`
  --> libsurfer/src/translation/mod.rs:88:35
   |
88 |             AnyTranslator::Python(t) => {}
   |                                   ^ help: if this is intentional, prefix it with an underscore: `_t`
   |
   = note: `#[warn(unused_variables)]` on by default

warning: unused variable: `t`
   --> libsurfer/src/translation/mod.rs:141:35
    |
141 |             AnyTranslator::Python(t) => None,
    |                                   ^ help: if this is intentional, prefix it with an underscore: `_t`

warning: `libsurfer` (lib) generated 2 warnings
error: could not compile `libsurfer` (lib) due to 1 previous error; 2 warnings emitted

However, building surfer with cargo build --release seems to work. I would suggest to temporarily change the cargo build --release --frozen --all-features to cargo build --release