openssl3 @3.2.1: does not respect minos or sdk settings on build

[lukaso (Lukas Oberhuber)]

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

      cmd LC_BUILD_VERSION
  cmdsize 32
 platform 1
    minos 13.0
      sdk 13.3
   ntools 1
     tool 3
  version 857.1

This looks very similar to #69944

[lukaso (Lukas Oberhuber)]

This appears to be happening only on the x86_64 build and not on the arm build.

[neverpanic (Clemens Lang)]

Do you happen to know which environment variables or command line flags one would have to set to control those fields?

[ryandesign (Ryan Carsten Schmidt)]

I would guess the minos field would come from the deployment target that was actually used, which would be based on the MACOSX_DEPLOYMENT_TARGET environment variable which MacPorts automatically sets in all phases, unless the build system overrides that by using either the old -macosx_version_min= or the new -macos_version_min= flags.

I would guess the sdk field would be set based on which SDK was actually used. MacPorts automatically passes -isysroot and -syslibroot flags to do that, unless this build is ignoring or overriding the MacPorts CFLAGS / CPPFLAGS / CXXFLAGS / LDFLAGS environment variables. MacPorts also sets the SDKROOT environment variable for projects that like to consume the SDK path that way. Some projects for example use xcrun --show-sdk-path to discover the SDK path, which will echo back SDKROOT if it is set to an SDK path that exists.