[MacPorts] #33454: Failed to install libvpx
MacPorts
noreply at macports.org
Thu Mar 22 11:53:31 PDT 2012
#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 |
--------------------------------+-------------------------------------------
Changes (by cal@…):
* status: reopened => closed
* resolution: => invalid
Comment:
Replying to [comment:23 anotherperson2011@…]:
> The contents of ''macports.conf" have never been modified and have the
toolchain path set to "developer_dir
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain"
, which seems correct.
If `macports.conf` wasn't modified the setting for `developer_dir` would
be commented. A value of
`/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain`
is _not_ the correct value; as stated above, please use
`/Applications/Xcode.app/Contents/Developer/` or do not set the setting at
all to let MacPorts automatically detect the correct path.
> {{{
> :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:24>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list