Bug 695192 – games-fps/gzdoom-4.2.1 : virtmem.cpp:(.text+<snip>): undefined reference to shm_open

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Toralf Förster 2019-09-20 14:40:15 UTC]

/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: libraries/asmjit/libasmjit.a(virtmem.cpp.o): in function `asmjit::VirtMem_openAnonymousMemory(int*, bool)':
virtmem.cpp:(.text+0x24c): undefined reference to `shm_open'
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: virtmem.cpp:(.text+0x268): undefined reference to `shm_unlink'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_desktop_plasma-libressl-20190913-195803

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-9.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby24 (with Rubygems)
  [2]   ruby25 (with Rubygems) *
Available Rust versions:
  [1]   rust-1.37.0 *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.13.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

repository timestamp:

==> /var/db/repos/gentoo/metadata/timestamp.chk <==
Thu, 19 Sep 2019 23:26:16 +0000

emerge -qpvO games-fps/gzdoom
[ebuild     U ] games-fps/gzdoom-4.2.1 [4.2.0] USE="gtk nonfree openmp -gtk2"

[Comment 1 Toralf Förster 2019-09-20 14:40:19 UTC]

Created attachment 590404 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2019-09-20 14:40:21 UTC]

Created attachment 590406 [details]
emerge-history.txt

[Comment 3 Toralf Förster 2019-09-20 14:40:24 UTC]

Created attachment 590408 [details]
environment

[Comment 4 Toralf Förster 2019-09-20 14:40:27 UTC]

Created attachment 590410 [details]
etc.portage.tbz2

[Comment 5 Toralf Förster 2019-09-20 14:40:30 UTC]

Created attachment 590412 [details]
games-fps:gzdoom-4.2.1:20190920-004401.log.bz2

[Comment 6 Toralf Förster 2019-09-20 14:40:32 UTC]

Created attachment 590414 [details]
logs.tbz2

[Comment 7 Toralf Förster 2019-09-20 14:40:35 UTC]

Created attachment 590416 [details]
temp.tbz2

[Comment 8 James Le Cuirot 2019-09-20 21:16:30 UTC]

*** Bug 695196 has been marked as a duplicate of this bug. ***

[Comment 9 James Le Cuirot 2019-09-20 21:18:43 UTC]

I'm not able to reproduce this but I think it may be due to the linking order. Could you try this again but when it fails, rerun the failing command manually, moving -lrt to after libraries/asmjit/libasmjit.a in the list.

[Comment 10 jospezial 2019-09-21 14:54:58 UTC]

(In reply to James Le Cuirot from comment #9)
> I'm not able to reproduce this but I think it may be due to the linking
> order. Could you try this again but when it fails, rerun the failing command
> manually, moving -lrt to after libraries/asmjit/libasmjit.a in the list.

After configure phase adding that change to
/var/tmp/portage/games-fps/gzdoom-4.2.1/work/gzdoom-4.2.1_build/build.ninja
works.
How to change that in the source as normal patch or sed before configure?

[Comment 11 William Breathitt Gray 2019-09-25 22:40:28 UTC]

I'm having trouble recreating this error as well. It seems like something wrong with the GZDoom CMake configuration.

Are you able to verify whether the same error occurs with the vanilla GZDoom 4.2.1 release (https://github.com/coelckers/gzdoom/archive/g4.2.1.tar.gz) without the Gentoo patches. That should let us know if the problem is something that needs to be fixed upstream.

[Comment 12 James Le Cuirot 2019-09-25 22:52:41 UTC]

It's okay, I understand the problem. The linking order is wrong and I'll prepare a patch when I get a minute. Whether it affects you or not probably depends on USE flags but not necessarily against this package.

[Comment 13 James Le Cuirot 2019-09-26 20:39:50 UTC]

Created attachment 591134 [details, diff]
Patch against gzdoom

Please try this patch before I send it upstream.

[Comment 14 James Le Cuirot 2019-10-20 11:45:01 UTC]

Ping? I really don't want to send this upstream if I'm not sure whether it helps.

[Comment 15 Toralf Förster 2019-10-20 12:41:25 UTC]

(In reply to James Le Cuirot from comment #13)
> Created attachment 591134 [details, diff] [details, diff]
> Patch against gzdoom
> 
> Please try this patch before I send it upstream.

works

[Comment 16 Larry the Git Cow 2019-10-24 20:37:03 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3faf4a588314618d2747164741de1918205ffbf3

commit 3faf4a588314618d2747164741de1918205ffbf3
Author:     James Le Cuirot <[e-mail]>
AuthorDate: 2019-10-24 20:36:30 +0000
Commit:     James Le Cuirot <[e-mail]>
CommitDate: 2019-10-24 20:36:30 +0000

    games-fps/gzdoom: Version bump to 4.2.3
    
    The shm_open issue with libasmjit has gone away, at least temporarily,
    because upstream have reverted to an older version that doesn't use
    librt.
    
    Closes: https://bugs.gentoo.org/695192
    Package-Manager: Portage-2.3.77, Repoman-2.3.17
    Signed-off-by: James Le Cuirot <[e-mail]>

 games-fps/gzdoom/Manifest                                 |  2 +-
 .../gzdoom-4.2.1-Introduce-the-BUILD_NONFREE-option.patch | 15 +++++++--------
 .../gzdoom/{gzdoom-4.2.1.ebuild => gzdoom-4.2.3.ebuild}   |  5 +++--
 3 files changed, 11 insertions(+), 11 deletions(-)