[MacPorts] #59360: libvpx: configure.sdkroot: command not found

MacPorts noreply at macports.org
Fri Oct 18 01:36:06 UTC 2019


#59360: libvpx: configure.sdkroot: command not found
-------------------------+----------------------
  Reporter:  ryandesign  |      Owner:  dbevans
      Type:  defect      |     Status:  accepted
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.1
Resolution:              |   Keywords:
      Port:  libvpx      |
-------------------------+----------------------

Comment (by Gcenx):

 Replying to [comment:10 ryandesign]:
 > In shell syntax, `$(SDKROOT)` is ''not'' how you would refer to an
 environment variable named SDKROOT*; that's how you would refer to a shell
 command or function named SDKROOT, and there isn't one. If you had wanted
 to refer to an environment variable named SDKROOT, you would need to use
 `${SDKROOT}` or `$SDKROOT`—but MacPorts doesn't set an environment
 variable called SDKROOT either. You could modify the port to do so.
 However:

 I didn't even notice I hadn't replaced `(` with `{` and `)` with `}` dumb
 mistake on my part.....
 \\
 I had added an environment variable within my offline Portfile the issue
 was the above.
 \\
 \\
 > When MacPorts wants a port to use an SDK, it already supplies the needed
 `-isysroot`/`-syslibroot` flags to do so in `CFLAGS`/`CXXFLAGS`/`LDFLAGS`.
 If the build system is already picking up those values, there's no need
 for the build system to manually add more SDK flags, so I would just
 remove any code it has that does that. (And if the build system is ''not''
 honoring the `CFLAGS`/`CXXFLAGS`/`LDFLAGS` MacPorts supplies, then
 ''that's'' what needs to be fixed.)
 >
 > *`$(SDKROOT)` ''is'' one of the two valid ways to refer to a
 ''Makefile'' variable called SDKROOT (the other valid way being
 `${SDKROOT}`), but the configure.sh script is not a Makefile.
 \\
 Thank you for the explanation, I'm still rather new to how macports
 handles things.
 \\
 Since `libvpx` builds regardless then the patch in comment:1 that would be
 the correct way then.

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


More information about the macports-tickets mailing list