boost183-libs is setup to coexist with boost-libs and openmw has no problem with having both present and will use boost-libs .
However boost183 and boost DO conflict.
boost183 is only needed during building collada-dom and should be removed after that build has finished .
Building in a clean chroot will do this for you automatically,
In case your chosen build method doesn't remove built deps then you need to do that yourself .
TL;DR: remove boost183
If that doesn't help, post full build output somewhere public so others can look at it.
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