Search Criteria
Package Details: surfer-waveform-git 0.3.0.r216.gcaab1e0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/surfer-waveform-git.git (read-only, click to copy) |
|---|---|
| Package Base: | surfer-waveform-git |
| Description: | A waveform viewer with a focus on a snappy usable interface, and extensibility. |
| Upstream URL: | https://gitlab.com/surfer-project/surfer |
| Licenses: | EUPL-1.2 |
| Conflicts: | surfer-waveform |
| Provides: | surfer-waveform |
| Submitter: | delta64 |
| Maintainer: | delta64 (TheZoq2) |
| Last Packager: | delta64 |
| Votes: | 2 |
| Popularity: | 0.049398 |
| First Submitted: | 2024-02-27 23:49 (UTC) |
| Last Updated: | 2025-07-06 17:44 (UTC) |
Dependencies (10)
- openssl (openssl-gitAUR, openssl-staticAUR, openssl-aegisAUR)
- python
- binutils (make)
- cargo (rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-gitAUR, rust, rustup) (make)
- desktop-file-utils (desktop-file-utils-gitAUR) (make)
- gcc (gcc-gitAUR, gccrs-gitAUR, gcc-snapshotAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- rust (rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-gitAUR, rustup) (make)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR) (check)
- freetype2 (freetype2-qdoled-aw3225qfAUR, freetype2-gitAUR, freetype2-macosAUR, freetype2-qdoledAUR) (check)
Latest Comments
1 2 Next › Last »
5hayanB commented on 2025-08-10 05:41 (UTC) (edited on 2025-08-10 09:04 (UTC) by 5hayanB)
After debugging, I found that there was indeed a discrepancy in
RUSTFLAGS.RUSTFLAGSwas not set when building from source, but was gettingRUSTFLAGS=-C force-frame-pointers=yes -C debuginfo=2 --remap-path-prefix=$HOME/surfer-waveform-git/src=/usr/src/debug/surfer-waveform-gitwhen usingmakepkg. Exporting theRUSTFLAGSfrom themakepkgenvironment while building from source also results in OOM. Adding!debugto theoptionsarray inPKGBUILDfixes the OOM error. Any reason not to add!debugin thePKGBUILD?delta64 commented on 2025-08-09 13:19 (UTC)
Please try
makepkgrather thanparu. 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.
5hayanB commented on 2025-08-09 12:47 (UTC)
I am building
surferfrom source via the following commands.These commands are also present in the
build()function of thePKGBUILD. Building from source compiles successfully but installing viaparugets OOM killed. Following are the flags in mymakepkg.conf.LTOFLAGSwon't matter due tooptions=(!lto)inPKGBUILD.Also, https://gitlab.com/surfer-project/surfer/-/issues/424 was resolved so
sed -i 's/#!\[deny(unused_crate_dependencies)\]//g' libsurfer/src/lib.rscan be removed now.delta64 commented on 2025-07-13 23:22 (UTC)
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.5hayanB commented on 2025-07-12 13:44 (UTC)
I am getting OOM errors when building
surferviaparu. However, following the build steps defined in thePKGBUILD(exporting the environment variables and executingcargo build --release --frozen --all-features) and buildingsurferfrom a freshly cloned repository, it is successfully building and no OOM errors are being reported. What could be going wrong?delta64 commented on 2025-07-06 17:45 (UTC)
Thanks, I've added a sed to workaround it and reported this upstream: https://gitlab.com/surfer-project/surfer/-/issues/424
5hayanB commented on 2025-07-05 12:55 (UTC)
I am getting the following error.
However, building surfer with
cargo build --releaseseems to work. I would suggest to temporarily change thecargo build --release --frozen --all-featurestocargo build --release5hayanB commented on 2025-03-22 20:05 (UTC)
Yeah, it was getting OOM killed. Thank you.
delta64 commented on 2025-03-17 23:12 (UTC)
Still works for me, but I notice a lot of memory usage during the build, so I guess you got OOM killed. Check logs from your system to confirm.
5hayanB commented on 2025-03-10 13:12 (UTC)
Error while building package.
1 2 Next › Last »