Opened 5 months ago
Last modified 5 months ago
#69944 assigned defect
zstd @1.5.6: does not respect macos setting on build
| Reported by: | lukaso (Lukas Oberhuber) | Owned by: | MarcusCalhoun |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | zstd |
Description
Even after setting this, the build still leaves zstd build for the MacOS version it is running on:
echo 'macosx_deployment_target 10.13' | tee -a ${PREFIX}/etc/macports/macports.conf
echo 'macosx_sdk_version 10.13' | tee -a ${PREFIX}/etc/macports/macports.conf
From otool -l
Load command 10
cmd LC_BUILD_VERSION
cmdsize 32
platform 1
minos 13.0
sdk 13.3
ntools 1
tool 3
version 857.1
Change History (6)
comment:1 Changed 5 months ago by lukaso (Lukas Oberhuber)
comment:2 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | set to MarcusCalhoun |
|---|---|
| Status: | new → assigned |
| Summary: | zstd @ 1.5.6: does not respect macos setting on build → zstd @1.5.6: does not respect macos setting on build |
comment:3 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
Do you check each library manually or is there an easy way to audit all of the libraries that your program depends on to find the ones that have this problem?
comment:4 Changed 5 months ago by lukaso (Lukas Oberhuber)
I’ve written a program to check it (or should I say, chat-gpt wrote me a program to check it.) Happy to upload if it would be helpful.
But in this instance it came via a bug report as I’d not incorporated the script into the CI system.
comment:6 Changed 5 months ago by ryandesign (Ryan Carsten Schmidt)
I was just curious for my own purposes whether you had to parse the otool -l output or if there was a better API for getting just the interesting values, and how you were collecting the list of libraries that you needed to check.
It looks like this bug was introduced upstream in v1.5.6