[SOLVED] SBo package for mame-mame240 build error

twy · 06-05-2022, 02:38 PM

I'm trying to build mame 0.240 using the SBo on slackware64-15.0,

https://slackbuilds.org/repository/15.0/games/mame/

and I'm getting this error:

Code:

Linking floptool...
/usr/bin/ccache /usr/bin/clang++ -o ../../../../../floptool ../../../../linux_clang/obj/x64/Release/src/tools/floptool.o ../../../../linux_clang/obj/x64/Release/src/tools/image_handler.o ../../../../linux_clang/obj/x64/Release/generated/version.o     -L"../../../../../../../../usr/X11/lib" -L"../../../../../../../../usr/X11R6/lib" -L"../../../../../../../../usr/openwin/lib" -L"." -L"../../../../linux_clang/bin/x64/Release/mame_mame" -L"../../../../linux_clang/bin/x64/Release" -m64 -fuse-ld=gold -Wl,-rpath,/usr/lib64 -Wl,--enable-new-dtags ../../../../linux_clang/bin/x64/Release/mame_mame/libformats.a ../../../../linux_clang/bin/x64/Release/libutils.a ../../../../linux_clang/bin/x64/Release/lib7z.a ../../../../linux_clang/bin/x64/Release/mame_mame/libocore_sdl.a ../../../../linux_clang/bin/x64/Release/libutf8proc.a -ldl -lrt -lSDL2 -lm -lpthread -lutil -lexpat -lz -lFLAC
/usr/bin/ld.gold: error: cannot open ../../../../../../../../usr/X11/lib/libdl.so: No such file or directory
/usr/bin/ld.gold: error: cannot open ../../../../../../../../usr/X11/lib/librt.so: No such file or directory
/usr/bin/ld.gold: error: cannot open ../../../../../../../../usr/X11/lib/libm.so: No such file or directory
/usr/bin/ld.gold: error: cannot open ../../../../../../../../usr/X11/lib/libutil.so: No such file or directory
/usr/bin/ld.gold: error: cannot open ../../../../../../../../usr/X11/lib/libFLAC.so: No such file or directory
/usr/bin/ld.gold: error: cannot open ../../../../../../../../usr/X11/lib/libm.so: No such file or directory
../../../../linux_clang/bin/x64/Release/mame_mame/libocore_sdl.a(posixptty.o):posixptty.cpp:function posix_open_ptty(unsigned int, std::unique_ptr<osd_file, std::default_delete<osd_file> >&, unsigned long&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&): error: undefined reference to 'openpty'
clang-13: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [floptool.make:267: ../../../../../floptool] Error 1
make[1]: *** [Makefile:1228: floptool] Error 2
make[1]: *** Waiting for unfinished jobs....

It continues to build more files for a while after this error, but then ends with these messages:

Code:

make[1]: Leaving directory '/tmp/SBo/mame-mame0240/build/projects/sdl/mame/gmake-linux-clang'
make: *** [makefile:1302: linux_x64_clang] Error 2

Any ideas on how to fix this?

twy · 06-05-2022, 02:56 PM

Right now, I am trying

Code:

USE_CCACHE="no" MAKEFLAGS="-j8" ./mame.SlackBuild

So, I will have to wait now to see what happens...

edit:
Getting the same problem using the above. It is as if it is trying to compile 32-bit. I'm running pure 64-bit slackware, no multilib. But, this compile should not be trying to build 32-bit anyway.

Daedra · 06-05-2022, 03:33 PM

I just tested it on my machine and it compiled fine. Not sure where your problem is coming from, but I did see this in the README..

Quote:

This build requires around 3.5GB of storage in /tmp (or whatever you
set TMP to in the environment).

twy · 06-05-2022, 03:35 PM

Btw... I have just gone ahead (for now) and reinstalled my old mame-0.194-x86_64-1_SBo package from slackware64-14.2. It still works fine. I think that, when it comes to mame, it would be nice to see SBo packages for many versions of mame offered on slackbuilds.org. Sometimes, the new version has problems and you want to go back to an older version (like mame-0.194 works nicely). I don't have the mame 0.194 slackbuild files anymore - hope I don't need to try to rebuild it!

Is there a way to download old SBo package versions?

Still, the mame 0.240 SBo should work. I still want to see the build problem fixed, if anyone can help with that.

ponce · 06-05-2022, 04:26 PM

Quote:

Originally Posted by twy

Is there a way to download old SBo package versions?

you can try navigating the git tree: first you open https://git.slackbuilds.org/slackbuilds/ then you put in the search box "games/mame" and click "search".
at this point you can click on the commit you prefer (for example "games/mame: Updated for version 0.194."), on the resulting page click on "tree" and then navigate the tree to games/mame: when you see the files you can download them clicking on the "plain" link to their right.

FWIW 0.240 built fine here too (tried also on a multilib install, because I was curious to try that too).

twy · 06-05-2022, 06:00 PM

I am starting to think that the problem is my system.

I have upgradepkg --reinstall all packages with *glibc* and have also reinstalled all the packages in the d/ (development) package set. But, the build of mame still has the same problem.

Now, I going to try compiling an alternate kernel. If it compiles, I'll try to run on it. Then, try compiling mame again. I have no idea what the problem is. If it works for everyone else, then something is corrupted on my system.

twy · 06-06-2022, 12:31 AM

If I just do

Code:

tar xvf mame-mame0240.tar.gz
cd mame-mame0240
make -j8

then it builds without any problem. It produces (after a long compile) a large mame executable file right there, and it works fine. I ran it and played a game.

The mame.SlackBuild is trying to do something that will not work on my system, which is an upgraded slackware64-14.2 -> 15.0. It used to be multilib, but I did not reinstall multilib. I did a full slackpkg clean-system before beginning to reinstall SBo packages. I reinstalled the whole d/ (development) set of packages just to be sure. I suppose I could try reinstalling all of the l/ packages. Not sure what difference that could make. I also recompiled and reinstalled my kernel (regenerating the initrd too). The kernel compiles okay.

Maybe someone can test the mame.SlackBuild on a clean VM installation without multilib.

ponce · 06-06-2022, 02:09 AM

Quote:

Originally Posted by ponce

FWIW 0.240 built fine here too (tried also on a multilib install, because I was curious to try that too).

maybe I wasn't clear but, FWIW, I have already tried also on a non-multilib install...

twy · 06-06-2022, 10:06 AM

It fixed the problem on my end. It builds now.

I had to clean /usr/lib so that it matches a fresh slackware64-15.0 install. I also cleaned /etc/ld.so.conf. Then, ran ldconfig. After this, the build works.

My /usr/lib had many broken symlinks to libraries that had been removed when I removed (slackpkg clean-system) the slackware64-14.2 multilib. I also removed some other old directories. Just to be sure, I reinstalled certain packages to make sure they don't put something back in /usr/lib. The nvidia driver installation put some files (libGL libEGL) in /usr/lib. I'm going to uninstall the driver, check /usr/lib and clear nvidia-related files, reinstall mesa, then install the nvidia driver again without 32-bit support and see what goes in /usr/lib.

Here is my /etc/ld.so.conf now:

Code:

include /etc/ld.so.conf.d/*.conf
/lib64
/usr/lib64
/usr/local/lib64
/usr/x86_64-slackware-linux/lib64

And here is how my /usr/lib looks now:

Code:

total 720
drwxr-xr-x 6 root root   4096 Sep 27  2021 NetworkManager/
drwxr-xr-x 3 root root   4096 Feb 13  2021 crda/
drwxr-xr-x 2 root root   4096 Jun  6 04:30 distcc/
drwxr-xr-x 3 root root   4096 Sep 27  2021 firewalld/
drwxr-xr-x 2 root root   4096 May 30 22:29 geeqie/
drwxr-xr-x 2 root root   4096 Aug 29  2021 ldscripts/
lrwxrwxrwx 1 root root     13 May 31 01:56 libEGL.so.1 -> libEGL.so.1.0*
-rwxr-xr-x 1 root root 105496 Jul 11  2012 libEGL.so.1.0*
lrwxrwxrwx 1 root root     12 May 31 01:56 libGL.so.1 -> libGL.so.1.2*
-rwxr-xr-x 1 root root 439248 Jul 11  2012 libGL.so.1.2*
drwxr-xr-x 2 root root   4096 Nov  3  2021 libear/
-rwxr-xr-x 1 root root 129912 Nov  3  2021 libomptarget.rtl.amdgpu.so*
drwxr-xr-x 3 root root   4096 Nov  3  2021 libscanbuild/
drwxr-xr-x 2 root root   4096 Jun  6 09:04 nvidia/
drwxr-xr-x 2 root root   4096 May 27 00:50 pkgconfig/
drwxr-xr-x 2 root root   4096 Mar 13 03:37 polkit-1/
drwxr-xr-x 6 root root   4096 May 30 23:29 rpm/
drwxr-xr-x 2 root root   4096 Nov 30  2021 siconv/
drwxr-xr-x 4 root root   4096 Jan  5 04:49 systemd/

Again, I am going to recheck what the nvidia driver really installs.

I hope this might be helpful to anyone else (?) that has this problem after upgrading from a multilib to a non-multilib slackware.