clang-15 fails to build on Leopard 10.5 i386

[rmottola (Riccardo)]

build fails, full log attached. I see several suspect things>

:info:configure sh: /bin/ps: Operation not permitted
:info:configure sh: /bin/ps: Operation not permitted
:info:configure -- The C compiler identification is unknown
:info:configure sh: /bin/ps: Operation not permitted
:info:configure sh: /bin/ps: Operation not permitted
:info:configure sh: /bin/ps: Operation not permitted
:info:configure sh: /bin/ps: Operation not permitted

ps works usually... what-s going on wrong?

later I see this:

:info:configure CMake Error at CMakeLists.txt:54 (project):
:info:configure   The CMAKE_C_COMPILER:
:info:configure     /opt/local/bin/clang-mp-13
:info:configure   is not a full path to an existing compiler tool.

clang 13 should be is in the dependency list, but is not yet build or present in my system. But perhaps this error is bogus because of the failed detection before? Latest clang on this system is 11, which already did build as dependency during upgrade (ld64)

[rmottola (Riccardo)]

10.5 i386 build

[mascguy (Christopher Nielsen)]

I helped Kirill validate builds for the various Clang ports on 10.5, but with the caveat that it was limited to 64-bit.

Whether it's possible to support 10.5 32-bit, though, is another question entirely.

Kirill, Ken, anyone... thoughts on 32-bit feasibility...?

[kencu (Ken)]

this doesn't look like a 32 bit problem -- I don't know exactly why yet, but clang-13 is supposed to be a build dep but is not being called in as a build dep, so the build fails.

Riccardo -- did you do some funny kind of installation here, or just sudo port -v install clang-15? Because if you just did that, a whole bunch of deps should be listed in your main.log, and for whatever reason, they are not. No deps are listed at all.

(To be noted that all clangs newer than clang-11 are not functional on systems older than 10.7 unless the linker is updated to something newer than what is currently the buildbot default linker.)

[rmottola (Riccardo)]

Indeed, it doesn't look like a 32bit issue (yet). Also, 10.5 64bit is a strange beast, I do run it (upgrading on my other MacBook right now) but I guess most people use 10.5 on PPC (32 or 64) and 32bit intel.

I didn't install clang explicitly, it got pulled in through some dependencies. I think it was ld64, but it disappeared after a selfupdate... hmm. Perhaps something was fixed/removed within a few hours?

I have some failures if I just upgrade all outdated, let's see if I can reproduce reliably with a specific port.