[MacPorts] #61321: libtool, apr: SDK path is baked into installed files (was: apr-util @1.6.1_2 +no_bdb fails to build (due to wrong sysroot?))

[MacPorts]

#61321: libtool, apr: SDK path is baked into installed files
--------------------------+----------------------
  Reporter:  pierswalter  |      Owner:  larryv
      Type:  defect       |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.6.3
Resolution:               |   Keywords:
      Port:  apr libtool  |
--------------------------+----------------------
Changes (by ryandesign):

 * cc: danielluke (added)
 * owner:  danielluke => larryv
 * port:  apr-util apr => apr libtool


Comment:

 The SDK path gets baked into the files installed by the libtool port.

 {{{
 $ grep SDK /opt/local/bin/glibtool
 /opt/local/bin/glibtool:LTCFLAGS="-pipe -Os
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -arch
 x86_64"
 }}}

 apr bundles and installs a copy of libtool so this affects the apr port
 too.

 {{{
 $ grep SDK /opt/local/share/apr-1/build/libtool
 /opt/local/share/apr-1/build/apr_rules.mk
 /opt/local/share/apr-1/build/libtool:LTCFLAGS="-pipe -Os
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -arch
 x86_64"
 /opt/local/share/apr-1/build/apr_rules.mk:CFLAGS=-pipe -Os
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -arch
 x86_64
 /opt/local/share/apr-1/build/apr_rules.mk:CPPFLAGS=-I/opt/local/include
 -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk
 /opt/local/share/apr-1/build/apr_rules.mk:LDFLAGS=-L/opt/local/lib
 -Wl,-headerpad_max_install_names
 -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk
 -arch x86_64
 $
 }}}

 The SDK path that gets baked in is the one from the command line tools, if
 the command line tools are installed, which they are on our build
 machines. You probably got a binary of apr from our build machines which
 is why that's the path it's looking for on your system.

 You can avoid the problem by installing the command line tools or by
 rebuilding apr from source using `sudo port -ns upgrade --force apr`.
 Then, if you don't have the command line tools installed, the SDK path
 that will be baked in will be the Xcode SDK path.

 If `xcode-select --install` does not work to install the command line
 tools you can download the installer from the
 [https://developer.apple.com/download/more/?=Command%20Line%20Tools Apple
 developer downloads web site].

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