Compilation falling under Mac OS

[epaell]

Apologies if this is due to something silly on my behalf but I'm trying to compile cpm65 under Mac OS (15.5) on an ARM-based Mac. I thought I had all dependencies installed but I get the following when I try to run make:

`~/local/src/cpm65$ make LLVM=$HOME/llvm-mos/bin/

build/ab.mk:81: .obj/build.mk: No such file or directory
build/ab.mk:81: .obj/build.mk: No such file or directory
AB
loading build.py
loading build/pkg.py
Error materialising Target("+libelf"): <function package at 0x1015944a0>
Arguments: {'self': Target("+libelf"), "name": "+libelf", "package": "libelf", "fallback": None, "dir": "$(OBJ)/+libelf"}
Traceback (most recent call last):
File "/Users/len067/local/src/cpm65/build/ab.py", line 623, in
main()
File "/Users/len067/local/src/cpm65/build/ab.py", line 619, in main
t.materialise()
File "/Users/len067/local/src/cpm65/build/ab.py", line 288, in materialise
raise e
File "/Users/len067/local/src/cpm65/build/ab.py", line 283, in materialise
self.callback(**cbargs)
File "build/pkg.py", line 71, in package
_package(self, name, package, fallback, TargetPkgConfig)
File "build/pkg.py", line 52, in _package
fallback
AssertionError: Required package "libelf" not installed when materialising target "$[name]"
make: *** No rule to make target "+all", needed by "all". Stop.`

I have tried to install libelf (despite it not being listed as a dependency) but it still doesn't appear to find it.

Any guidance would be greatly appreciated.

[davidgiven]

I haven't tried building it on OSX, so your mileage may vary...

The build system looks for dependencies with pkg-config, so you'll need to install libelf via a way which causes the .pc file to be present. For other projects I use Homebrew for this; you don't say whether you're using that or not. You'll also need gmake, not the default make in OSX which is too old.

[epaell]

Thanks David - that's given me some hints of where to look.

Yes, I used Homebrew to install libelf. Turns out I also had some miniconda in the path and so pkg-config was looking in the wrong place for the .pc files. So I rejigged the PATH to ensure it looks in Homebrew first. I also installed gmake (you are right, make didn't get very far). I then ran into issues with readline (which I had to add a specific path for in PKG_CONFIG_PATH). Then it needed "chronic", so installed that. It now gets through about 20% of the build but fails with compilation errors in src/arch/neo6502:

[86/427] LLVMCC src/arch/neo6502/+bios_obj
tools/multilink.cc:33:14: error: no member named 'filesystem' in namespace 'std'
   33 |     if (std::filesystem::file_size(f1) != std::filesystem::file_size(f2))
      |         ~~~~~^

I'll have a closer look at this when I get a chance.

[davidgiven]

std::filesystem is C++17. This suggests your compiler is old enough that it defaults to an earlier version. You might try adding --std=c++17 to the CFLAGS definition in the Makefile.

[epaell]

Thanks again David.

I couldn't add it to CFLAGS (because it would then fail when compiling the C sources) but managed to check whether this was the issue by adding it directly to build/c.py for the CXX side of things (I could be wrong but it seemed like the CXXFLAGS wasn't used there). That allowed it to get further but then ran into a compilation problem in tools/xextobin.cc where it had an error with types in "ifs.seekg(ifs.tellg() - 2L);" - I changed this to "ifs.seekg(-2L, std::ios_base::cur);" and it proceeded further. Unfortunately, it is now running into this error:

[167/397] LLVMCLINK third_party/pascal-m/+loader
error: 8-bit reference to 16-bit address 0x41e at relo 18, address 0x68?
error: 8-bit reference to 16-bit address 0x30010 at relo 2, address 0x29?
error: 8-bit reference to 16-bit address 0x207 at relo 101, address 0x1e2?
mos-cpm65-clang: error: ld.lld command failed with exit code 1 (use -v to see invocation)
mos-cpm65-clang: error: ld.lld command failed with exit code 1 (use -v to see invocation)
mos-cpm65-clang: error: ld.lld command failed with exit code 1 (use -v to see invocation)

Perhaps if it is too much trouble I'll just try to switch over to a Linux build when I get the opportunity (I just don't have a Linux system handy at the moment - the closest I have is a Raspberry PI installation).