[MacPorts] #33454: Failed to install libvpx

[MacPorts]

#33454: Failed to install libvpx
--------------------------------+-------------------------------------------
  Reporter:  proutyo@…          |       Owner:  macports-tickets@…                   
      Type:  defect             |      Status:  closed                               
  Priority:  Normal             |   Milestone:                                       
 Component:  ports              |     Version:  2.0.4                                
Resolution:  invalid            |    Keywords:                                       
      Port:  libvpx             |  
--------------------------------+-------------------------------------------

Comment(by anotherperson2011@…):

 Replying to [comment:24 cal@…]:
 > please use `/Applications/Xcode.app/Contents/Developer/`

 Using this did not fix the issue.
 Also, upon inspection, /usr/bin/clang *is* installed, so don't understand
 why configure says it cannot find it.

 >or do not set the setting at all to let MacPorts automatically detect the
 correct path.
 Re-commenting out the 'developer_dir' line *did* fix the issue.
 Thank you very much.


 >
 > > {{{
 > > :info:configure Unable to invoke compiler: /usr/bin/clang -O2 -arch
 x86_64 -isysroot  -mmacosx-version-min=10.7 -m64 -fomit-frame-pointer
 -arch x86_64 -O3 -fPIC -Wall -Wdeclaration-after-statement -Wdisabled-
 optimization -Wpointer-arith -Wtype-limits -Wcast-qual -Wno-unused-
 function
 > > }}}
 > >
 > > The failure seems to be due to the wrong compiler path being sought.
 Instead of "/usr/bin/clang" it ought to be "usr/bin/clang" (relative to
 $developer_dir).[[BR]]This issue does not occur with other Macport
 packages, it seems to be a bug in the libvpx configurator.
 >
 > No, the compiler path is correct. Please install the Command Line Tools
 from the Xcode Preferences' Downloads tab if you haven't already. This is
 required for MacPorts as documented in the guide, and the package contains
 `/usr/bin/clang`. The compiler invocation fails because of a bogus
 `-isysroot` flag without a path, which happens when there's no SDK found
 in `$sdk_dir`, which is
 `$developer_dir/Platforms/MacOSX.platform/Developer/SDKs`. This is also
 the reason why the value for `developer_dir` cannot be what you mentioned
 above.

-- 
Ticket URL: <https://trac.macports.org/ticket/33454#comment:25>
MacPorts <http://www.macports.org/>
Ports system for Mac OS