Thanks! Pushed update to disable lto.
As for -j for make - that is up to makepkg.conf configuration (see MAKEFLAGS). Each user can set up however many cpu's they want for compilation there. PKGBUILD should not force that.
| Git Clone URL: | https://aur.archlinux.org/far2l-git.git (read-only, click to copy) |
|---|---|
| Package Base: | far2l-git |
| Description: | Linux port of FAR v2 |
| Upstream URL: | https://github.com/elfmz/far2l |
| Licenses: | GPL2 |
| Conflicts: | far2l, far2l-gui, far2l-ttyx |
| Provides: | far2l, far2l-gui, far2l-ttyx |
| Submitter: | mmozeiko |
| Maintainer: | mmozeiko |
| Last Packager: | mmozeiko |
| Votes: | 28 |
| Popularity: | 0.024703 |
| First Submitted: | 2016-12-14 00:40 (UTC) |
| Last Updated: | 2026-08-28 03:08 (UTC) |
Thanks! Pushed update to disable lto.
As for -j for make - that is up to makepkg.conf configuration (see MAKEFLAGS). Each user can set up however many cpu's they want for compilation there. PKGBUILD should not force that.
@mmozeiko
After recent updates to the gcc and binutils, the package build fails with a lot of errors like these:
undefined reference to `std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::_M_mutate(unsigned long, unsigned long, wchar_t const*, unsigned long)'
fatal error: ld terminated with signal 11 [Segmentation fault], core dumped
As a workaround, you can disable LTO by adding the line:
options=('!lto')
I also suggest replacing the last command with this one to speed up the build process:
cmake --build "$srcdir"/far2l/build --target install -j$(nproc --ignore=1)
@mmozeiko Thanks. It seems everything's ok now.
Updated to have separate build folder, if using AUR helper like yay or similar then make sure to clean the cache folder before rebuilding.
@mmozeiko
After splitting PKGBUILD into build() and package(), the package now includes an extra CMakeFiles directory under /usr/share/far2l/themes (which leads to a garbage entry in the Options->Colors menu). It looks like this might be happening because CMake is run directly in the source tree, and the CMakeFiles folder created during configuration ends up being installed. The themes/CMakeLists.txt uses file(GLOB children ...), which picks up CMakeFiles as a subdirectory and treats it as a theme. Maybe switching to an out-of-source build (i.e., creating a separate build directory and running CMake from there) would help. That way all temporary CMake files stay inside the build directory and are not packaged.
https://github.com/elfmz/far2l/pull/2707 Workaround for CMake 4.0 is not needed anymore. Thanks for maintaining this package for years!
CMake Error at CMakeLists.txt:3 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier.
Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
Thanks, I've updated build.
https://github.com/elfmz/far2l/commit/745d38c4a24325c215969a7c3ebee40959db4a09 Seems like we don't need pcre anymore.
@mmozeiko thanks, works now
Pinned Comments
mmozeiko commented on 2023-12-19 06:51 (UTC) (edited on 2023-12-19 06:51 (UTC) by mmozeiko)
This is "git" package. There's no need to flag package out-of-date when far2l has a new release version.