Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#33454 closed defect (invalid)

Failed to install libvpx

Reported by: proutyo@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.4
Keywords: Cc: mparchet@…, neverpanic (Clemens Lang)
Port: libvpx

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Log for libvpx is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/libvpx/main.log
Error: The following dependencies were not installed: kdelibs4 soprano strigi ffmpeg libvpx openjpeg jbigkit lcms2 schroedinger orc speex texi2html x264 virtuoso gawk kdepimlibs4 akonadi mysql5-server mysql5 mysql5 gpgme libassuan libgpg-error pth libical prison libdmtx ImageMagick ghostscript jbig2dec libpaper xorg-libXt urw-fonts webp qrencode lensfun libgphoto2 gd2 xpm libexif libgpod libplist swig-python bison swig py27-mutagen taglib libkdcraw libkexiv2 exiv2 libkipi libksane sane-backends net-snmp liblqr marble libkdeedu opencv faac faad2 liboil oxygen-icons

Attachments (8)

main.log (5.2 KB) - added by heruan@… 12 years ago.
main.2.log (129.4 KB) - added by heruan@… 12 years ago.
main.3.log (11.3 KB) - added by mparchet@… 12 years ago.
main.4.log (4.4 KB) - added by jeffrey.kane.johnson@… 12 years ago.
libvpx, unable to invoke compiler
main.5.log (8.7 KB) - added by jeffrey.kane.johnson@… 12 years ago.
libvpx, unable to invoke compiler (clean build attempt)
config.err (5.7 KB) - added by jeffrey.kane.johnson@… 12 years ago.
libvpx, unable to invoke compiler (clean build attempt)
configure.sh (30.2 KB) - added by jeffrey.kane.johnson@… 12 years ago.
error-out-xcodeversion.patch (353 bytes) - added by neverpanic (Clemens Lang) 12 years ago.
Patch against the libvpx Portfile, printing the value of $xcodeversion as error message.

Download all attachments as: .zip

Change History (35)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Port: libvpx added

Please attach the aforementioned log file.

Changed 12 years ago by heruan@…

Attachment: main.log added

comment:2 Changed 12 years ago by neverpanic (Clemens Lang)

The log doesn't show a clean build attempt. Please run sudo port clean libvpx, retry and attach the new main.log.

Changed 12 years ago by heruan@…

Attachment: main.2.log added

Changed 12 years ago by mparchet@…

Attachment: main.3.log added

comment:3 Changed 12 years ago by mparchet@…

Cc: mparchet@… added

Cc Me!

comment:4 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

mparchet, your log is also incomplete, and shows a totally different error:

:info:configure Unable to invoke compiler: /usr/bin/cc -pipe -O2 -m64 -isysroot  -mmacosx-version-min=10.7 -m64 -fomit-frame-pointer -arch x86_64 -O3 -fPIC -Wall -Wdeclaration-after-statement -Wdisabled-optimization -Wpointer-arith -Wcast-qual -Wno-unused-function
:info:configure
:info:configure Configuration failed. This could reflect a misconfiguration of your
:info:configure toolchains, improper options selected, or another problem. If you
:info:configure don't see any useful error messages above, the next step is to look
:info:configure at the configure error log file (config.err) to determine what
:info:configure configure was trying to do when it died.

You could examine the config.err file, but I suspect it means you have Xcode 4.3 and have not set it up properly. Perhaps you have not installed the required command line tools. Consult MacPorts documentation or ask on the macports-users mailing list if you need help doing that.

comment:5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

heruan, your log shows you are on the pre-release of Mountain Lion and thus presumably the pre-release of Xcode 4.4. We really can't help with pre-release versions of OS X and Xcode, and it may violate your Apple non-disclosure agreement to discuss it publicly. I doubt it's a MacPorts problem anyway; it's probably either a bug in libvpx or in OS X or Xcode, so please report the problem to the people who can fix it.

proutyo, please attach your main.log so we can see which of these or any other problem you're experiencing.

comment:6 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: heruan@… added

Changed 12 years ago by jeffrey.kane.johnson@…

Attachment: main.4.log added

libvpx, unable to invoke compiler

comment:7 in reply to:  4 Changed 12 years ago by jeffrey.kane.johnson@…

I'm also getting the "Unable to invoke compiler" error (just uploaded my log file). I'm on Lion 10.7.3 with Xcode 4.3. Other ports configure and build fine (updated Boost last night); it seems to just be having trouble with this one.

comment:8 Changed 12 years ago by neverpanic (Clemens Lang)

Your log does not show a clean build attempt. Please run port clean libvpx and try again. Also please attach config.log from $(port work libvpx)/libvpx-v1.0.0.

comment:9 Changed 12 years ago by neverpanic (Clemens Lang)

Cc: cal@… added

Cc Me!

Changed 12 years ago by jeffrey.kane.johnson@…

Attachment: main.5.log added

libvpx, unable to invoke compiler (clean build attempt)

Changed 12 years ago by jeffrey.kane.johnson@…

Attachment: config.err added

libvpx, unable to invoke compiler (clean build attempt)

comment:10 in reply to:  8 Changed 12 years ago by jeffrey.kane.johnson@…

Replying to cal@…:

Your log does not show a clean build attempt. Please run port clean libvpx and try again. Also please attach config.log from $(port work libvpx)/libvpx-v1.0.0.

Hm, thought it was clean, sorry about that. I've uploaded a new main.log. I didn't have a config.log file, but I did have a config.err files, so I've attached that one.

comment:11 Changed 12 years ago by neverpanic (Clemens Lang)

Resolution: duplicate
Status: newclosed

heruan, your problem is a different one and should be tracked in a different bug report, if any, since we cannot support pre-release versions of OS X.

mparchet, jeffrey.kane.johnson, your problem is a duplicate of #33283, which is already fixed by r90164. Please run selfupdate, clean the port and try again.

The original reporter did not attach the main.log despite asking for it, so there's nothing more that can be done here. I'm closing this as duplicate, although it is duplicate for mparchet and jeffrey.kane.johnson, invalid for heruan and invalid with lack-of-interest for proutyo.

comment:12 in reply to:  11 ; Changed 12 years ago by jeffrey.kane.johnson@…

Replying to cal@…:

heruan, your problem is a different one and should be tracked in a different bug report, if any, since we cannot support pre-release versions of OS X.

mparchet, jeffrey.kane.johnson, your problem is a duplicate of #33283, which is already fixed by r90164. Please run selfupdate, clean the port and try again.

The original reporter did not attach the main.log despite asking for it, so there's nothing more that can be done here. I'm closing this as duplicate, although it is duplicate for mparchet and jeffrey.kane.johnson, invalid for heruan and invalid with lack-of-interest for proutyo.

That's what I've been doing. Here's my console output:

:~ jj56$ sudo port selfupdate
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.0.4 installed,
MacPorts base version 2.0.4 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
:~ jj56$ sudo port clean libvpx
--->  Cleaning libvpx
:~ jj56$ sudo port upgrade outdated
--->  Computing dependencies for libvpx
--->  Fetching archive for libvpx
--->  Attempting to fetch libvpx-1.0.0_0.darwin_11.x86_64.tgz from http://packages.macports.org/libvpx
--->  Fetching libvpx
--->  Verifying checksum(s) for libvpx
--->  Extracting libvpx
--->  Applying patches to libvpx
--->  Configuring libvpx
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
Log for libvpx is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/libvpx/main.log
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

Has that fix been rolled out, or do I need to do something differently to get it?

comment:13 in reply to:  12 Changed 12 years ago by jeffrey.kane.johnson@…

And, actually, I just noticed that that fix is for an earlier version of libvpx; perhaps that's the problem?

comment:14 Changed 12 years ago by neverpanic (Clemens Lang)

The fix should have been rolled out automatically. Although there is a delay between commit to version control and rollout to users this delay should have been passed long ago.

Please:

  • verify your libvpx Portfile (port file libvpx will tell you where it is) matches the one on source:/trunk/dports/multimedia/libvpx/Portfile@90164:33-38, especially the highlighted lines.
  • verify xcode-select -print-path returns /Applications/Xcode.app/Contents/Developer or the respective path inside the Xcode.app bundle, in case you moved that
  • verify /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs exists and contains at least one SDK.

What do you mean by "an earlier version of libvpx"? MacPorts only provides one version of libvpx as far as I can see and the fix has been made against this version, which is the version you are trying to install.

comment:15 Changed 12 years ago by heruan@…

Cc: heruan@… removed

Cc Me!

comment:16 in reply to:  14 Changed 12 years ago by jeffrey.kane.johnson@…

Replying to cal@…:

The fix should have been rolled out automatically. Although there is a delay between commit to version control and rollout to users this delay should have been passed long ago.

Please:

  • verify your libvpx Portfile (port file libvpx will tell you where it is) matches the one on source:/trunk/dports/multimedia/libvpx/Portfile@90164:33-38, especially the highlighted lines.
  • verify xcode-select -print-path returns /Applications/Xcode.app/Contents/Developer or the respective path inside the Xcode.app bundle, in case you moved that
  • verify /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs exists and contains at least one SDK.

What do you mean by "an earlier version of libvpx"? MacPorts only provides one version of libvpx as far as I can see and the fix has been made against this version, which is the version you are trying to install.

Just that ticket #33283 lists libvpx @0.9.7-p1, and the current version is 1.0.0. All these things check out on my end: the portfile is identical, xcode-select points to the Developer folder in the app bundle, and I have 10.6 and 10.7 SDK's installed.

comment:17 Changed 12 years ago by neverpanic (Clemens Lang)

Resolution: duplicate
Status: closedreopened

While the issue was reported against libvpx 0.9.7-p1 I fixed it in 1.0.0, so this is definitely not the problem.

Can you attach $(port work libvpx)/libvpx-v1.0.0/build/make/configure.sh?

Changed 12 years ago by jeffrey.kane.johnson@…

Attachment: configure.sh added

comment:18 Changed 12 years ago by neverpanic (Clemens Lang)

Apparently your $xcodeversion variable is not 4.3 as it should be. What does xcodebuild -version print? What is your setting for $developer_dir in $prefix/etc/macports/macports.conf?

Can you apply the attached patch against the portfile, try again and paste the error message? You will have to revert the patch after that to get the port back into a working state.

Changed 12 years ago by neverpanic (Clemens Lang)

Patch against the libvpx Portfile, printing the value of $xcodeversion as error message.

comment:19 in reply to:  18 Changed 12 years ago by jeffrey.kane.johnson@…

Here's what I get running the patched Portfile:

jj56$ sudo port upgrade outdated
Portfile changed since last build; discarding previous state.
--->  Computing dependencies for libvpx
--->  Fetching archive for libvpx
--->  Attempting to fetch libvpx-1.0.0_0.darwin_11.x86_64.tgz from http://packages.macports.org/libvpx
--->  Fetching libvpx
--->  Verifying checksum(s) for libvpx
--->  Extracting libvpx
--->  Applying patches to libvpx
Error: Target org.macports.patch returned: Version: 4.3
Log for libvpx is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_libvpx/libvpx/main.log
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

And here's the output from xcodebuild -version:

jj56$ xcodebuild -version
Xcode 4.3
Build version 4E109

However, $developer_dir in my macports.conf file is /Developer. If I change that to /Applications/Xcode.app/Contents/Developer, it seems to work. So that must not have gotten updated somewhere along the line?

comment:20 Changed 12 years ago by neverpanic (Clemens Lang)

Resolution: invalid
Status: reopenedclosed

MacPorts never automatically changes a setting a user set in $prefix/etc/macports/macports.conf. However, this setting is commented in the default (source:trunk/base/doc/macports.conf.in@90058:18). Likely you changed it; please change it back or comment it to let MacPorts figure out where the developer dir is.

Apparently a lot of people changed this variable when MacPorts wasn't ready for Xcode 4.3 based on some blog posts, posts on stackoverflow.com and on twitter. Unfortunately, this was counterproductive to the real and correct fix (which is upgrading to MacPorts 2.0.4) and should be changed back (just in case somebody reads this).

comment:21 Changed 12 years ago by jeffrey.kane.johnson@…

Ah. I've never edited the macports.conf file, but version 1.8 of macports did not have that option commented out, so it must have been carried along as I've been upgrading. Thanks for your help.

comment:22 Changed 12 years ago by neverpanic (Clemens Lang)

r90802 contains a patch warning about possibly outdated developer_dir settings.

comment:23 Changed 12 years ago by anotherperson2011@…

Resolution: invalid
Status: closedreopened

Similar failure seen here with Xcode 4.3.1, even after performing all checks listed above and doing 'sudo port clean libvpx' followed by 'sudo port upgrade outdated'. 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. The failure is:

: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).
This issue does not occur with other Macport packages, it seems to be a bug in the libvpx configurator.

comment:24 in reply to:  23 ; Changed 12 years ago by neverpanic (Clemens Lang)

Resolution: invalid
Status: reopenedclosed

Replying to 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).
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.

comment:25 in reply to:  24 Changed 12 years ago by anotherperson2011@…

Replying to 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).
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.

comment:26 Changed 12 years ago by ua3qrz@…

Thank you very much for the tip! I've got the configuration failure on libvpx when install ffmpeg. The only help was your post regarding "/Developer" dir in macports config file. When I've commented out the "developer_dir" all went just fine. Thanks a lot.

sudo vi /opt/local/etc/macports/macports.conf # Directory containing Xcode Tools #developer_dir /Developer :x!

sudo port clean libvpx sudo port install libvpx

comment:27 in reply to:  26 Changed 12 years ago by startup@…

Replying to ua3qrz@…:

Thank you very much for the tip! I've got the configuration failure on libvpx when install ffmpeg. The only help was your post regarding "/Developer" dir in macports config file. When I've commented out the "developer_dir" all went just fine. Thanks a lot.

sudo vi /opt/local/etc/macports/macports.conf # Directory containing Xcode Tools #developer_dir /Developer :x!

sudo port clean libvpx sudo port install libvpx

FYI : this also worked for me! I'm on Mac OS X Lion 10.7.3 with XCode 4.3.2 with command line tools installed.

Note: See TracTickets for help on using tickets.