sdlmame-0182

[NeddySeagoon]

Team,

In unsupported software as it a copy the ebuild and change the version version bump.
On amd64 I get ...

* mame-0.182.zip SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking mame-0.182.zip to /var/tmp/portage/games-emulation/sdlmame-0.182/work
>>> Unpacking ./mame.zip to /var/tmp/portage/games-emulation/sdlmame-0.182/work
3rdparty/pugixml/tests/data/#U0442#U0435#U0441#U0442.xml: mismatching "local" filename (3rdparty/pugixml/tests/data/????????.xml),
continuing with "central" filename version
* ERROR: games-emulation/sdlmame-0.182::gentoo_static failed (unpack phase):

On arm64 it works. At least, it unpacks, builds but takes forever to link in only 1G RAM.
I did think I might cross compile mame for arm64 on amd64 but its the same unpacking routine.
I've tried fetching mame-0.182.zip several times to no effect. As I run http-replicator, it will come from my server cache anyway, so I'm confident I have identical mame-0.182.zip files in both places.

I've also tried

[Ant P.]

I'm going to take a stab in the dark... maybe locale settings differ between the two boxes?

unzip's also given me headaches with corrupting unicode filenames on unpack, so I'm kind of interested in finding an answer to this myself. I've been using p7zip as a workaround, but I guess it's kind of hard to do that with ebuilds.

[NeddySeagoon]

Ant P.

I can confirm its UTF-8 symbols in filenames.
With using different decompressors and different options, I can get three or four different renderings of the UTF-8 symbols in the build directory.
None of which are right of course.

The arm64 version works because I hacked the ebuild to ignore a similar error in an older version of mame.
I had forgotten that.

0.182 seems to have a build problem that may or may not be related to that file name being mangled.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.