| Git Clone URL: | https://aur.archlinux.org/openmw-git.git (read-only, click to copy) |
|---|---|
| Package Base: | openmw-git |
| Description: | An open-source engine reimplementation for the role-playing game Morrowind. |
| Upstream URL: | http://www.openmw.org |
| Licenses: | custom, MIT, GPL-3.0-or-later |
| Conflicts: | openmw |
| Provides: | openmw |
| Submitter: | None |
| Maintainer: | bwrsandman (Lone_Wolf) |
| Last Packager: | Lone_Wolf |
| Votes: | 33 |
| Popularity: | 0.50 |
| First Submitted: | 2011-01-05 16:17 (UTC) |
| Last Updated: | 2025-09-07 19:16 (UTC) |
After running multiple tests that confirmed the issue only occurs with LTO builds & lua mods installed I uploaded a crash log with debug symbols to upstream.
More testing confirmed that adding the flag -fno-omit-frame-pointer prevents the bug from happening.
On non-lto builds the flag doesn't appear to cause problems, so the workaround is now applied in the openmw-git package.
LTO is default enabled for archlinux clean chroot builds using devtools but can be disabled by setting options(=!lto) in the PKGBUILD.
ADDED: disabling lto build does prevent the crash from happening.
Hi, I'm just a novice but, if i understand correctly, the pb appear only if we build with LTO. But build with LTO is not a standard build, it's not the default (no?). So a good compromise would be to add, in the PKGBUILD, a comment with the "-fno-omit-frame-pointer" flag and an explanation, so the ones who want to build with LTO just have to uncomment the flag, no?
The screenshots of aur openmw-git users you posted are the first proof I've seen this bug does affect openmw-git.
I'll create clean chroot builds (including debug symbols) and test them on on a clean openmw install with ncgdmw lua 4.4.7 (downloaded from nexus).
Okay. I've posted four of the conversations I've had with users of openmw-git that are affected on #8601, and tagged you.
Good enough, or should I take a bunch more time out of my day to rebuild with LTO also?
Perhaps I didn't make my point of view clear enough .
The reports in archlinux gitlab, modding-openmw issues, openmw issues all show the archlinux repo openmw 0.49 build had a problem that was solved by adding a flag.
Upstream (openmw devs) have not gotten enough info to determine the cause of the issue. Show proof that this crash happens on openmw-git by posting the openmw crash log here or on https://gitlab.com/OpenMW/openmw/-/issues/8601 so it can be investigated further by upstream.
Until there's proof this package is affected by that bug I see no reason to add a flag that's not recommended/deemed necessary by upstream.
S3ctor wants to remind you to add the cmake flag to the PKGBUILD:
CXXFLAGS="${CXXFLAGS/-fno-omit-frame-pointer/}"
because as it stands now without it, you crash when you access your settings in game when you have certain mods like the dynamic leveling one.
Thanks
The upstream issue is https://gitlab.com/OpenMW/openmw/-/issues/8601
Note that openmw-git uses different builds/versions of several dependencies then repo openmw does. A big difference is the openscenegraph version .
We also don't enable LTO builds but do include debug symbols .
Please verify if the issue occurs with ncgdmw-lua and openmw-git .
Certain mod configurations cause crashes when Openmw is built on arch linux with LTO. While this is an upstream bug which is still being investigated, the official arch linux package has solved said crash by building with -fno-omit-frame-pointer. It would be awesome if you could add that argument to the pkgbuild!
See https://gitlab.archlinux.org/archlinux/packaging/packages/openmw/-/issues/4 for more details.
@unknown78 : Upstream finally decided to remove qt5 support and only use qt6 .
Pinned Comments
Lone_Wolf commented on 2022-06-17 10:07 (UTC)
openmw-git has been found to require a sizable amount of temporary space during building.
The available amount depends on system specifics so is different for all systems. In case build fails with "no space left on device" you may be bitten by this.
See https://bbs.archlinux.org/viewtopic.php?id=277304 for details and possible solutions.
bwrsandman commented on 2016-09-24 14:59 (UTC) (edited on 2018-11-22 17:28 (UTC) by bwrsandman)
Please refrain from flagging the git version as out date when a new release comes out. The git aur packages update their version on install time based on the tags of the git repo.
Keep in mind that this is a VCS package and it is meant to be in line with the latest master which might not always work. It is not meant to follow the release pattern in any particularly smart way and assumes that upstream maintains their tags consistently.
For the newest release, the correct page is https://www.archlinux.org/packages/?q=openmw