|
|
|
|
Joined: Dec 2005
Posts: 108
Senior Member
|
OP
Senior Member
Joined: Dec 2005
Posts: 108 |
Hi, I compile mame for macos myself by cloning the github source, then running make. Lately, I keep getting errors like this:
Archiving libformats.a...
fatal error: /Library/Developer/CommandLineTools/usr/bin/ranlib: can't move the output file to its final location: ../../../../osx_clang/bin/x64/Release/mame_mame/libformats.a (Resource busy)
/Library/Developer/CommandLineTools/usr/bin/ar: internal ranlib command failed
make[2]: *** [../../../../osx_clang/bin/x64/Release/mame_mame/libformats.a] Error 1
make[1]: *** [formats] Error 2
make: *** [macosx_x64_clang] Error 2
If I run make again it fails at a different point. Not sure what's wrong here... any ideas?
|
|
|
|
|
Joined: Sep 2000
Posts: 232
Senior Member
|
|
Senior Member
Joined: Sep 2000
Posts: 232 |
I just compiled mame from the GitHub source yesterday without a problem. I'm running 10.15.1 and SDL 2.0.10
Have you installed the latest Xcode? Tell us which macOS version you're running and what kind of Mac you have.
=will=
|
|
|
|
|
Joined: Dec 2005
Posts: 108
Senior Member
|
|
OP
Senior Member
Joined: Dec 2005
Posts: 108 |
macos ver 10.15.1
Mac Mini 2018
3 GHz 6-Core Intel Core i5
I am using Command Line Tools
clang -v
Apple clang version 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin19.0.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Last edited by CRP; 11/12/19 09:01 PM.
|
|
|
|
|
Joined: Sep 2000
Posts: 232
Senior Member
|
|
Senior Member
Joined: Sep 2000
Posts: 232 |
I have a slightly newer clang (?) - don't know if installing latest Xcode would help.
clang -v
Apple clang version 11.0.0 (clang-1100.0.33.12)
Target: x86_64-apple-darwin19.0.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
=will=
|
|
|
|
|
Joined: Mar 2001
Posts: 16,680 Likes: 4
Very Senior Member
|
Very Senior Member
Joined: Mar 2001
Posts: 16,680 Likes: 4 |
Is MAME running when you're trying to compile? That's usually what "Resource busy" means. I build at least once a day on my MacBook Pro and haven't had any problems.
|
|
|
|
|
Joined: Dec 2005
Posts: 108
Senior Member
|
|
OP
Senior Member
Joined: Dec 2005
Posts: 108 |
no, mame is not running. I am really at a loss about these errors...
|
|
|
|
|
Joined: Dec 2005
Posts: 108
Senior Member
|
|
OP
Senior Member
Joined: Dec 2005
Posts: 108 |
I was compiling with the source files on my NAS. If I compile with files on the local HD everything works fine. Not sure what the NAS is doing, but it generates those Resource Busy messages...
|
|
|
|
|
Joined: Mar 2004
Posts: 665
Senior Member
|
|
Senior Member
Joined: Mar 2004
Posts: 665 |
Probably the latency introduced by the NAS is causing race conditions.
|
|
|
|
|
Joined: Oct 2019
Posts: 21
Member
|
|
Member
Joined: Oct 2019
Posts: 21 |
Agreed. You can try adjusting your parallel build level to see if you can accomplish a build from NAS. Of course -j1 should avoid race conditions, but will be very, very slow...
|
|
|
|
|
Joined: Mar 2001
Posts: 16,680 Likes: 4
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 16,680 Likes: 4 |
Is the NAS mounted via NFS or SMB? In my experience, NFS on macOS got flakey somewhere around 10.9 or 10.10 and hasn't improved since. I switched my MacBook to use SMB mounts instead of NFS and it's been totally stable (and gotten faster transfers).
|
|
|
|
0 members (),
32
guests, and
1
robot. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
Forums9
Topics8,882
Posts116,798
Members4,962
| |
Most Online890
Jan 17th, 2020
|
|
|
|
|
|
