py-ujson @5.5.0: doesn't build for the requested C++ stdlib

[ryandesign (Ryan Carsten Schmidt)]

py-ujson doesn't build for the requested C++ stdlib:

$ port -q outdated
py310-ujson                    5.5.0_0 < 5.5.0_0  (C++ stdlib libstdc++ != libc++)  

$ otool -L   /opt/bblocal/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/ujson.cpython-310-darwin.so
/opt/bblocal/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/ujson.cpython-310-darwin.so:
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

[reneeotten (Renee Otten)]

sorry for the trouble Ryan. The port appears to build fine though on all systems according to the status page. I have no access to such old OSes and no way to test this, and thus afraid I will not be of much help here.

[kencu (Ken)]

​https://github.com/macports/macports-ports/pull/16383

$ uname -a
Darwin Kens-107-VM-Parallels.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64


$ otool -L   /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/ujson.cpython-310-darwin.so
/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/ujson.cpython-310-darwin.so:
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 28.4.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

[kencu (Ken)]

[678386b74d8158b0cd72e54f3cae561ff144d29d/macports-ports]

[ryandesign (Ryan Carsten Schmidt)]

Replying to reneeotten:

The port appears to build fine though on all systems according to the status page.

It built "fine", but was broken according to rev-upgrade due to the use of the wrong C++ stdlib on 10.7 and 10.8.

I have no access to such old OSes and no way to test this, and thus afraid I will not be of much help here.

You can verify the problem and the fix on any OS version. You just need to look at the log and check whether the -stdlib=... flag is being supplied to every invocation of clang++.