 No.16509
Robbbert Senior Tester
Jun 5, 2019, 12:44
|
I do not know if we support this. Open for comments please. |
|---|---|
 No.16546
MrGW Tester
Jun 14, 2019, 15:39
|
Since I had experienced another issue with 0.210 (see bug report #7358) I figured I would pull the current source, compile and test again. Same issue for the RPi3 (ARM). 2 additional libraries are pulled in (libXext.so.6, libXi.so.6) and MAME will segfault just as it starts to render the UI. I realize ARM architecture may not be supported, but it has been working for over 2 years. Isn't there anyone else compiling MAME for the Raspberry Pi? |
 No.16547
Tafoid Administrator
Jun 14, 2019, 16:50
|
On team, I'm not sure. The project head hasn't been around much lately and I suspect he would have the most knowledge regarding alternative SDL (non-windows) builds. I do know there is someone who would regular compile on PI, but it appears he may no longer do it due to time taken? https://choccyhobnob.com/ Are you compiling it on the device or doing a cross compile? |
|
No.16548
MrGW Tester
Jun 14, 2019, 19:21
|
Hi Tafoid, I started doing a cross compile over a year ago using qemu on my Linux workstation. It cut the compile down from 16+ hours to about 2 hours. Big difference. As I had mentioned, things have been working very well up until 0.210. I'm sure it has to do with those new libraries, but can't figure out why they were added (or even needed). MAME is a huge project and the fact the source compiled under Raspbian says a lot about the quality of each release. I'm always so impressed by what these MAME developers do. Hopefully this issue can be identified and resolved. Perhaps some Makefile directives that get around this? Thanks for your continued efforts in helping. I do appreciate it. |
|
No.16569
MrGW Tester
Jun 19, 2019, 14:18
|
Latest update: Thanks to George McMullen, it looks like we have a "fix" for the segfault. He discovered some differences in the the makefile from version 0.209 to 0.210 and here's his comments: "I haven't been able to do any compilation tests yet, but I've found some changes from v0209 to v0210 which may be headed in the right direction. In the makefile in v0210, there are two options: # NO_USE_XINPUT = 1 # NO_USE_XINPUT_WII_LIGHTGUN_HACK = 1 But in v0209 the first is set to 0 and the second one doesn't exist (it's new in v0210). i.e. # NO_USE_XINPUT = 0 Incidentally, these flags seem to be related to libXi. These flags are referenced in the following files: scripts/src/osd/sdl.lua scripts/src/osd/sdl_cfg.lua" I uncommented these new lines and everything seems to work again: NO_USE_XINPUT = 1 NO_USE_XINPUT_WII_LIGHTGUN_HACK = 1 Thanks again to George for helping with this issue! |
|
No.16570
Tafoid Administrator
Jun 19, 2019, 15:38
|
Glad it got sorted out. The commit that changed things was here: https://github.com/mamedev/mame/pull/5056 https://github.com/mamedev/mame/commit/16bbe847ef289d09cc5d3908d75462131a2b6aa5 |