[MacPorts] #59755: net-snmp @5.8 fails to address the correct SDK

[MacPorts]

#59755: net-snmp @5.8 fails to address the correct SDK
-----------------------+------------------------
  Reporter:  TP75      |      Owner:  ryandesign
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:
      Port:  net-snmp  |
-----------------------+------------------------

Comment (by ryandesign):

 Replying to [comment:5 TP75]:
 > ****Replying to [comment:2 ryandesign]:
 > > I see it's attempting to use multiple different SDKs:
 > >
 > > {{{
 > > -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk
 > > -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk
 > > -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk
 > >
 -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
 > > }}}
 > >
 > > Certainly it shouldn't be doing that, but do either of those paths
 exist on your system? **Which version of Xcode do you have?**
 >
 > Thank you for your kind advice and request.  Please find the results
 below.
 >
 > {{{
 > $ ls -la /Library/Developer/CommandLineTools/SDKs/
 >
 > drwxr-xr-x  7 root  wheel  224  9 Jul 02:07 MacOSX.sdk
 > lrwxr-xr-x  1 root  wheel   10 23 Nov 17:53 MacOSX10.14.sdk ->
 MacOSX.sdk
 >
 >
 > $ xcode-select --version
 > xcode-select version 2354.
 > }}}
 >
 > Please recall there is **no XCode installed** intentionally.

 Ok. I wasn't sure how it would behave with multiple `-isysroot`
 flags—whether it would try to use them all or just the first or last one.
 Since you definitely do have the path specified in the first, second and
 third `-isysroot` flags, but not the last one, I suspect only the last
 flag takes effect.

 The bad flag is likely coming from perl's config files. Perl loves to
 build its modules with the flags that had been used to build perl (which
 might have been built on our build server, where we do have Xcode
 installed). I would love it if perl would cease and desist doing that, but
 I don't know how to make it do that.


 Replying to [comment:7 TP75]:
 > Not installing XCode was intentionally but not
 [https://www.macports.org/install.php according the MacPorts installation]
 procedure, obviously. This was done  deliberately as an experiment.

 That's fine, assuming you'd like to encounter problems and help us work
 through resolving them. :) We would like to be able to support users who
 don't have Xcode installed, but have only just begun to add support for
 that in MacPorts 2.6.0. Prior to that, it was assumed that you have Xcode
 installed, and Xcode-relative SDK paths were used and in many cases got
 baked into ports inadvertently. As of MacPorts 2.6.0, we will use command-
 line-tools-relative SDK paths instead (unless a port indicates the need
 for Xcode by using `use_xcode yes`), but we still have an unknown probably
 large number of binary packages that we distribute that were built prior
 to MacPorts 2.6.0 and so still use Xcode-based SDK paths.

 > However, after **install of XCode** from the XCode_11-2.1.xip package
 **the net-snmp build still fails.**

 That's not surprising, since Xcode 11 doesn't contain the 10.14 SDK. Try
 installing [https://developer.apple.com/download/more/?=xcode%2010.3 Xcode
 10.3], which does contain the 10.14 SDK.

-- 
Ticket URL: <https://trac.macports.org/ticket/59755#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS