[MacPorts] #67836: clang-16 @16.0.6: error: aligned deallocation function of type 'void (void *, std::align_val_t) noexcept' is only available on macOS 10.13 or newer
MacPorts
noreply at macports.org
Fri Jul 28 04:25:05 UTC 2023
#67836: clang-16 @16.0.6: error: aligned deallocation function of type 'void (void
*, std::align_val_t) noexcept' is only available on macOS 10.13 or newer
---------------------------+--------------------------
Reporter: barracuda156 | Owner: (none)
Type: defect | Status: new
Priority: High | Milestone:
Component: ports | Version: 2.8.1
Resolution: | Keywords: mountainlion
Port: clang-16 |
---------------------------+--------------------------
Comment (by barracuda156):
Replying to [comment:5 ryandesign]:
> We had successful builds of clang @16.0.6 on all buildbot workers for
Mac OS X 10.6 and later on July 3-4.
I assume, `+universal` on Intel has not been tested?
> Comparing the buildbot log from 10.8 with yours, I see these
differences:
>
> * yours is building universal for i386 & x86_64 while the buildbot is
building only for x86_64 (this could be the relevant difference)
This is a likely suspect for the cause of the failure, but if universal is
broken, it is a serious problem. It has also been working fine at least
with Clang-14 and earlier; looks like I skipped building Clang-15 as
universal here.
> * yours found /opt/local/bin/git; buildbot found /usr/bin/git (probably
irrelevant)
This is because Macports tree is built against a bootstrap one, to make
`git` work, since system one is essentially defunct on < 10.9.
> * yours failed the `CXX_SUPPORTS_UNWINDLIB_NONE_FLAG` and
`COMPILER_RT_HAS_FUSE_LD_LLD_FLAG` tests; on the buildbot they succeeded
(maybe a consequence of building universal)
> * yours is building with `-j4` while the buildbot is using `-j8`
(probably irrelevant)
>
> Diffing the build phase of the two logs is not so easy since parallel
building means the lines are not in the same order between the two logs,
but looking at a few things manually:
>
> At the point in the log where yours fails, we're building target
cxxabi_static. On the buildbot it is using many warning flags like `-Wno-
user-defined-literals`. Your build isn't using that, which is why you see
the warnings `warning: user-defined literal suffixes not starting with '_'
are reserved [-Wuser-defined-literals]`.
>
> Before that, in the build phase, cmake is run again when it is trying to
build something using the just-built clang 16.0.6. This time, a relevant
difference between the two is that yours failed nearly all of the tests,
including the `CXX_SUPPORTS_FALIGNED_ALLOCATION_FLAG` test, while most
tests succeeded on the buildbot. That seems to match up with the ultimate
error you're getting about aligned deallocation not being supported.
Somewhat later I can try with Clang-15 to see if the failure existed
already back then, as well as try Clang-16 for i386. I would assume x86_64
without universal should work, since no other relevant differences from
buildbots.
--
Ticket URL: <https://trac.macports.org/ticket/67836#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list