bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/30930] ld-2.41 links mame in a way which gets stuck on aarch64


From: belegdol at gmail dot com
Subject: [Bug ld/30930] ld-2.41 links mame in a way which gets stuck on aarch64
Date: Mon, 02 Oct 2023 15:52:13 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=30930

--- Comment #6 from Julian Sikorski <belegdol at gmail dot com> ---
(In reply to Sam James from comment #2)
> Could you try give some instructions to reproduce manually from source,
> without using Fedora and Fedora specific tooling?
> 
> Bisecting binutils using 'git bisect run' + timeout would be helpful too if
> you can.

This might work, however I cannot test it unfortunately:
1. git clone https://github.com/mamedev/mame.git
2. Install deps according to the distros mechanism of choice
3. cd mame
4. make -O -j2 V=1 VERBOSE=1 NOWERROR=1 OPTIMIZE=2 PYTHON_EXECUTABLE=python3
QT_HOME=/usr/lib64/qt6 VERBOSE=1 USE_SYSTEM_LIB_ASIO=1 USE_SYSTEM_LIB_EXPAT=1
USE_SYSTEM_LIB_FLAC=1 USE_SYSTEM_LIB_GLM=1 USE_SYSTEM_LIB_JPEG=1
USE_SYSTEM_LIB_PORTAUDIO=1 USE_SYSTEM_LIB_PORTMIDI=1 USE_SYSTEM_LIB_PUGIXML=1
USE_SYSTEM_LIB_RAPIDJSON=1 USE_SYSTEM_LIB_SQLITE3=1 USE_SYSTEM_LIB_UTF8PROC=1
USE_SYSTEM_LIB_ZLIB=1 'SDL_INI_PATH=/etc/mame;' TOOLS=1 'OPT_FLAGS=-O2
-fexceptions -g1 -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang
-Werror=format-security -Werror=implicit-function-declaration
-Werror=implicit-int -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -mbranch-protection=standard
-fasynchronous-unwind-tables -fstack-clash-protection -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer' 'LDOPTS=-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -Wl,--build-id=sha1
-specs=/usr/lib/rpm/redhat/redhat-package-notes
5. ./mame -validate

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]