Home Page Forums Thread Like Summary - Look like Mingw is broken.

D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe and some other messages on the mame,exe building.
I closed the Malwarebytes program and it still coming up with the ld.exe issues. So I don't know why it showing these issues. lol

msys64-2022-01-12.exe

If there a update on this piece of tool. Please let me know.

Compiling resources generated/resource/mame_mame_vers.rc...
39132 driver(s) found
Compiling generated/mame/mame/drivlist.cpp...
Linking mame.exe...
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/bin/x64/Release/libemu.a(emumem_aspace.o):emumem_aspace.:(.text+0x85a): undefined reference to `vtable for address_space'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/bin/x64/Release/libemu.a(emumem_aspace.o):emumem_aspace.:(.text+0x8e7): undefined reference to `vtable for std::_Sp_counted_ptr_inplace<int, std::allocator<int>, (__gnu_cxx::_Lock_policy)2>'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/bin/x64/Release/libemu.a(emumem_aspace.o):emumem_aspace.:(.text+0x18fd): undefined reference to `vtable for address_space'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/bin/x64/Release/libemu.a(emumem_aspace.o):emumem_aspace.:(.text+0x1bb6): undefined reference to `vtable for std::_Sp_counted_ptr_inplace<emu::detail::memory_passthrough_handler_impl, std::allocator<emu::detail::memory_passthrough_handler_impl>, (__gnu_cxx::_Lock_policy)2>'

........ Skip the rest to here below.

D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/bin/x64/Release/libemu.a(emumem_aspace.o):emumem_aspace.:(.rdata$_ZTVSt23_Sp_counted_ptr_inplaceIN3emu6detail31memory_passthrough_handler_implESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE+0x8): undefined reference to `typeinfo for std::_Sp_counted_ptr_inplace<emu::detail::memory_passthrough_handler_impl, std::allocator<emu::detail::memory_passthrough_handler_impl>, (__gnu_cxx::_Lock_policy)2>'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: ../../../../mingw-gcc/bin/x64/Release/libemu.a(emumem_aspace.o):emumem_aspace.:(.rdata$_ZTVSt23_Sp_counted_ptr_inplaceIiSaIiELN9__gnu_cxx12_Lock_policyE2EE+0x8): undefined reference to `typeinfo for std::_Sp_counted_ptr_inplace<int, std::allocator<int>, (__gnu_cxx::_Lock_policy)2>'
collect2.exe: error: ld returned 1 exit status
mame.make:270: recipe for target '../../../../../mame.exe' failed
make[2]: *** [../../../../../mame.exe] Error 1
makefile:1099: recipe for target 'mame' failed
make[1]: *** [mame] Error 2
makefile:1118: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2

Works fine on Ubuntu. No problem there.

Use lld until the issue with GNU ld is resolved.

make -j8 ARCHOPTS="-fuse-ld=lld" REGENIE=1

worked for me. I had to look up how to pass the -fuse-ld=lld parameter.

Does rfka01's command line not work for people? In general you should prefer lld anyway because it's faster.