Opened 12 years ago

Closed 4 years ago

#35808 closed defect (fixed)

VirtualBox 4.1.20_0, fail to find libcrypto

Reported by: xl64100@… Owned by: royliu@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: anddam (Andrea D'Amore), ryandesign (Ryan Carsten Schmidt), royliu@…, edhem.bajric@…, nxwolverine@…, whcordis@…, jiri.tyr@…, gamperl@…, cooljeanius (Eric Gallager), kprussing (Keith), 1-61803
Port: virtualbox

Description (last modified by ci42)

I Can't upgrade virtualbox (was the same with 4.1.18 but I waited to see if it would be solved in next macports updates).

I get this log :

sudo port clean virtualbox
--->  Cleaning virtualbox

sudo port upgrade virtualbox                                                                                                                       
--->  Computing dependencies for virtualbox
--->  Fetching archive for virtualbox
--->  Attempting to fetch virtualbox-4.1.20_0+vde2+vnc.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/virtualbox
--->  Attempting to fetch virtualbox-4.1.20_0+vde2+vnc.darwin_11.x86_64.tbz2 from http://packages.macports.org/virtualbox
--->  Fetching distfiles for virtualbox
--->  Verifying checksum(s) for virtualbox
--->  Extracting virtualbox
--->  Applying patches to virtualbox
--->  Configuring virtualbox
Error: org.macports.configure for port virtualbox returned: configure failure: command execution failed
Please see the log file for port virtualbox for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

And in the main.log (attached) :

:info:configure Checking for ssl: 
:info:configure   libcrypto not found at -I/opt/local/include /opt/local/lib/libcrypto.dylib /opt/local/lib/libssl.dylib or openssl headers not found

Thanks for any help.

XL.

Attachments (7)

main.log (17.7 KB) - added by xl64100@… 12 years ago.
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/main.log
configure.log (67.2 KB) - added by xl64100@… 12 years ago.
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.1.20/configure.log
vbox-ssl-configure.cc (380 bytes) - added by anddam (Andrea D'Amore) 12 years ago.
compiled by configure script, actually failing
test-vbox-ssl-configure.sh (433 bytes) - added by anddam (Andrea D'Amore) 12 years ago.
command line used by configure script to compile vbox-ssl-configure.cc
patch-emulators-virtualbox-find-sdk.diff (2.4 KB) - added by pixilla (Bradley Giesbrecht) 12 years ago.
Use "xcode-select -print-path" in place of hardcoded /Developer.
main.2.log (83.5 KB) - added by nxwolverine@… 11 years ago.
Log file cataloguing problem installing Virtualbox on Mac OS X 10.6.8 with XCode 4.0.2
main.3.log (99.5 KB) - added by whcordis@… 10 years ago.
Build Log detailing failure of build on OS X 10.8.5 with XCode 5.0

Download all attachments as: .zip

Change History (48)

Changed 12 years ago by xl64100@…

Attachment: main.log added

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/main.log

comment:1 Changed 12 years ago by xl64100@…

Oups, didn't preview. How can I edit it to make it more readable ?

comment:2 Changed 12 years ago by xl64100@…

Tried to force rebuild openssl as I assumed it was the one providing the libcrypto library but this had no effect...

comment:3 Changed 12 years ago by ci42

Description: modified (diff)
Keywords: virtualbox libcrypto removed
Port: virtualbox added

comment:4 Changed 12 years ago by anddam (Andrea D'Amore)

Cc: and.damore@… ryandesign@… royliu@… added

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

The log also says:

Check the file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.1.20/configure.log for detailed error information.

Could you attach that file for us to look at?

Changed 12 years ago by xl64100@…

Attachment: configure.log added

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.1.20/configure.log

comment:6 Changed 12 years ago by pixilla (Bradley Giesbrecht)

Something must be wrong with your openssl installation. Please post the output of:

port contents openssl | grep -E '/opt/local/(include|lib)/'

Tried to force rebuild openssl

Are you saying the rebuild of openssl did not work? What was the command you used to force rebuild openssl?

This command should force openssl to rebuild: (man port: -n don't upgrade dependencies)

sudo port -n upgrade --force openssl

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

The errors in the configure.log you attached begin with:

error: cstdio: No such file or directory
error: stdlib.h: No such file or directory
error: stdio.h: No such file or directory
error: sys/types.h: No such file or directory
error: time.h: No such file or directory
error: string.h: No such file or directory
error: sys/time.h: No such file or directory

These are all standard system headers that should be present if you have installed Xcode correctly. Are you sure you have installed the Xcode command line tools? This is a separate step you need to do from within Xcode's Preferences window's Downloads section.

comment:8 in reply to:  7 Changed 12 years ago by anddam (Andrea D'Amore)

Replying to ryandesign@…:

The errors in the configure.log you attached begin with:

error: cstdio: No such file or directory
error: stdlib.h: No such file or directory
error: stdio.h: No such file or directory
error: sys/types.h: No such file or directory
error: time.h: No such file or directory
error: string.h: No such file or directory
error: sys/time.h: No such file or directory

These are all standard system headers that should be present if you have installed Xcode correctly. Are you sure you have installed the Xcode command line tools? This is a separate step you need to do from within Xcode's Preferences window's Downloads section.

I'm experiencing the same issue, I had command line tools installed for sure, recently I upgraded to 4.4.1 and installed them again. From Xcode preferences they are shown as installed as well.

I reverted up to two version bump of virtualbox port and still couldn't build it while I was certainly able to build it before, something's broken in tools setup.

I've isolated the C++ file used for testing by configure script and the actual failing build line, I'm attaching vbox-ssl-configure.cc and test-vbox-ssl-configure as minimal example. My output is

$ source test-vbox-ssl-configure.sh 
vbox-ssl-configure.cc:1:18: error: cstdio: No such file or directory
vbox-ssl-configure.cc:2:30: error: openssl/opensslv.h: No such file or directory
vbox-ssl-configure.cc:3:25: error: openssl/ssl.h: No such file or directory
vbox-ssl-configure.cc: In function 'int main()':
vbox-ssl-configure.cc:6: error: 'OPENSSL_VERSION_TEXT' was not declared in this scope
vbox-ssl-configure.cc:6: error: 'printf' was not declared in this scope
vbox-ssl-configure.cc:7: error: 'SSL_library_init' was not declared in this scope
$

I'm not confident with C++, where should cstdio be located?

Changed 12 years ago by anddam (Andrea D'Amore)

Attachment: vbox-ssl-configure.cc added

compiled by configure script, actually failing

Changed 12 years ago by anddam (Andrea D'Amore)

Attachment: test-vbox-ssl-configure.sh added

command line used by configure script to compile vbox-ssl-configure.cc

comment:9 Changed 12 years ago by royliu@…

Owner: changed from macports-tickets@… to royliu@…

What I suspect is going on is that you're on Lion (not Mountain Lion), and my new macosx_deployment_target math is causing problems.

@@ -92,9 +93,7 @@ if {${name} == ${subport}} {
 
         reinplace "s|@APPLICATIONS_DIR@|${applications_dir}|g" \
             ${worksrcpath}/LocalConfig.kmk
-    # TODO: The deployment target should be set dynamically, but, because of incompatibilities
-    # with OpenGL headers in 10.7, it's fixed at 10.6 for now.
-        reinplace "s|@MACOSX_DEPLOYMENT_TARGET@|10.6|g" \
+        reinplace "s|@MACOSX_DEPLOYMENT_TARGET@|10.[expr [lindex [split ${macosx_deployment_target} "."] 1] - 1]|g" \
            ${worksrcpath}/LocalConfig.kmk
         reinplace "s|@KEXT_DIR@|${prefix}${kext_dir}|g" \
             ${worksrcpath}/src/VBox/Installer/darwin/VBoxStartupItems/VirtualBox/VirtualBox

My MacPorts is a bit rusty. Is macosx_deployment_target derived from the OS version or the Xcode version? If it's the former, then the Portfile is trying to using Xcode 10.6, which doesn't exist in the newest version (only 10.7 and 10.8 supported).

comment:10 in reply to:  9 Changed 12 years ago by xl64100@…

Replying to royliu@…:

What I suspect is going on is that you're on Lion (not Mountain Lion), and my new macosx_deployment_target math is causing problems.

@@ -92,9 +93,7 @@ if {${name} == ${subport}} {
 
         reinplace "s|@APPLICATIONS_DIR@|${applications_dir}|g" \
             ${worksrcpath}/LocalConfig.kmk
-    # TODO: The deployment target should be set dynamically, but, because of incompatibilities
-    # with OpenGL headers in 10.7, it's fixed at 10.6 for now.
-        reinplace "s|@MACOSX_DEPLOYMENT_TARGET@|10.6|g" \
+        reinplace "s|@MACOSX_DEPLOYMENT_TARGET@|10.[expr [lindex [split ${macosx_deployment_target} "."] 1] - 1]|g" \
            ${worksrcpath}/LocalConfig.kmk
         reinplace "s|@KEXT_DIR@|${prefix}${kext_dir}|g" \
             ${worksrcpath}/src/VBox/Installer/darwin/VBoxStartupItems/VirtualBox/VirtualBox

My MacPorts is a bit rusty. Is macosx_deployment_target derived from the OS version or the Xcode version? If it's the former, then the Portfile is trying to using Xcode 10.6, which doesn't exist in the newest version (only 10.7 and 10.8 supported).

I'm using Lion, indeed. So you may have located the problem. Do you have a fix ?

XL.

comment:11 in reply to:  6 Changed 12 years ago by xl64100@…

Replying to pixilla@…:

Something must be wrong with your openssl installation. Please post the output of:

port contents openssl | grep -E '/opt/local/(include|lib)/'
  /opt/local/include/openssl/aes.h
  /opt/local/include/openssl/asn1.h
  /opt/local/include/openssl/asn1_mac.h
  /opt/local/include/openssl/asn1t.h
  /opt/local/include/openssl/bio.h
  /opt/local/include/openssl/blowfish.h
  /opt/local/include/openssl/bn.h
  /opt/local/include/openssl/buffer.h
  /opt/local/include/openssl/camellia.h
  /opt/local/include/openssl/cast.h
  /opt/local/include/openssl/cmac.h
  /opt/local/include/openssl/cms.h
  /opt/local/include/openssl/comp.h
  /opt/local/include/openssl/conf.h
  /opt/local/include/openssl/conf_api.h
  /opt/local/include/openssl/crypto.h
  /opt/local/include/openssl/des.h
  /opt/local/include/openssl/des_old.h
  /opt/local/include/openssl/dh.h
  /opt/local/include/openssl/dsa.h
  /opt/local/include/openssl/dso.h
  /opt/local/include/openssl/dtls1.h
  /opt/local/include/openssl/e_os2.h
  /opt/local/include/openssl/ebcdic.h
  /opt/local/include/openssl/ec.h
  /opt/local/include/openssl/ecdh.h
  /opt/local/include/openssl/ecdsa.h
  /opt/local/include/openssl/engine.h
  /opt/local/include/openssl/err.h
  /opt/local/include/openssl/evp.h
  /opt/local/include/openssl/hmac.h
  /opt/local/include/openssl/idea.h
  /opt/local/include/openssl/krb5_asn.h
  /opt/local/include/openssl/kssl.h
  /opt/local/include/openssl/lhash.h
  /opt/local/include/openssl/md4.h
  /opt/local/include/openssl/md5.h
  /opt/local/include/openssl/mdc2.h
  /opt/local/include/openssl/modes.h
  /opt/local/include/openssl/obj_mac.h
  /opt/local/include/openssl/objects.h
  /opt/local/include/openssl/ocsp.h
  /opt/local/include/openssl/opensslconf.h
  /opt/local/include/openssl/opensslv.h
  /opt/local/include/openssl/ossl_typ.h
  /opt/local/include/openssl/pem.h
  /opt/local/include/openssl/pem2.h
  /opt/local/include/openssl/pkcs12.h
  /opt/local/include/openssl/pkcs7.h
  /opt/local/include/openssl/pqueue.h
  /opt/local/include/openssl/rand.h
  /opt/local/include/openssl/rc2.h
  /opt/local/include/openssl/rc4.h
  /opt/local/include/openssl/ripemd.h
  /opt/local/include/openssl/rsa.h
  /opt/local/include/openssl/safestack.h
  /opt/local/include/openssl/seed.h
  /opt/local/include/openssl/sha.h
  /opt/local/include/openssl/srp.h
  /opt/local/include/openssl/srtp.h
  /opt/local/include/openssl/ssl.h
  /opt/local/include/openssl/ssl2.h
  /opt/local/include/openssl/ssl23.h
  /opt/local/include/openssl/ssl3.h
  /opt/local/include/openssl/stack.h
  /opt/local/include/openssl/symhacks.h
  /opt/local/include/openssl/tls1.h
  /opt/local/include/openssl/ts.h
  /opt/local/include/openssl/txt_db.h
  /opt/local/include/openssl/ui.h
  /opt/local/include/openssl/ui_compat.h
  /opt/local/include/openssl/whrlpool.h
  /opt/local/include/openssl/x509.h
  /opt/local/include/openssl/x509_vfy.h
  /opt/local/include/openssl/x509v3.h
  /opt/local/lib/engines/lib4758cca.dylib
  /opt/local/lib/engines/libaep.dylib
  /opt/local/lib/engines/libatalla.dylib
  /opt/local/lib/engines/libcapi.dylib
  /opt/local/lib/engines/libchil.dylib
  /opt/local/lib/engines/libcswift.dylib
  /opt/local/lib/engines/libgmp.dylib
  /opt/local/lib/engines/libgost.dylib
  /opt/local/lib/engines/libnuron.dylib
  /opt/local/lib/engines/libpadlock.dylib
  /opt/local/lib/engines/libsureware.dylib
  /opt/local/lib/engines/libubsec.dylib
  /opt/local/lib/libcrypto.1.0.0.dylib
  /opt/local/lib/libcrypto.a
  /opt/local/lib/libcrypto.dylib
  /opt/local/lib/libssl.1.0.0.dylib
  /opt/local/lib/libssl.a
  /opt/local/lib/libssl.dylib
  /opt/local/lib/pkgconfig/libcrypto.pc
  /opt/local/lib/pkgconfig/libssl.pc
  /opt/local/lib/pkgconfig/openssl.pc

Tried to force rebuild openssl

Are you saying the rebuild of openssl did not work? What was the command you used to force rebuild openssl?

This command should force openssl to rebuild: (man port: -n don't upgrade dependencies)

sudo port -n upgrade --force openssl

This is what I have done to rebuild openssl, it rebuilds but there was no effect on virtualbox compilation.

comment:12 in reply to:  7 Changed 12 years ago by xl64100@…

Replying to ryandesign@…:

The errors in the configure.log you attached begin with:

error: cstdio: No such file or directory
error: stdlib.h: No such file or directory
error: stdio.h: No such file or directory
error: sys/types.h: No such file or directory
error: time.h: No such file or directory
error: string.h: No such file or directory
error: sys/time.h: No such file or directory

These are all standard system headers that should be present if you have installed Xcode correctly. Are you sure you have installed the Xcode command line tools? This is a separate step you need to do from within Xcode's Preferences window's Downloads section.

I already installed the command line tools :/

comment:13 Changed 12 years ago by anddam (Andrea D'Amore)

Resolution: fixed
Status: newclosed

Replying to royliu@…:

What I suspect is going on is that you're on Lion (not Mountain Lion), and my new macosx_deployment_target math is causing problems.

It could but in this case the actual culprit is configure script that is assuming 10.6 is a valid SDK target on OS X 10.7, this isn't anymore the case since Xcode 4.4 and that's the reason why standard headers couldn't be find. I'm patching configure script and changing the reinplace to take care of $xcodeversion >= 4.4 case.

My MacPorts is a bit rusty. Is macosx_deployment_target derived from the OS version or the Xcode version? If it's the former, then the Portfile is trying to using Xcode 10.6, which doesn't exist in the newest version (only 10.7 and 10.8 supported).

It is, unless set in configuration file by the user.

The port now builds succesfully on my 10.7.4 system with Xcode 4.4.1, committed r97075, ticket closed.

comment:14 Changed 12 years ago by anddam (Andrea D'Amore)

I received buildbot failure reports from both lion buildbot and snowleopard buildbot, although with different errors.

Lion buildbot show the issue of this ticket even if I compile succesfully on Lion, can anyone confirm that after r97075 he can build virtualbox on a Lion system? I'm using Xcode 4.4.1 but I'd like to hear from a 4.3 install too.

comment:15 in reply to:  14 Changed 12 years ago by xl64100@…

Replying to and.damore@…:

I received buildbot failure reports from both lion buildbot and snowleopard buildbot, although with different errors.

Lion buildbot show the issue of this ticket even if I compile succesfully on Lion, can anyone confirm that after r97075 he can build virtualbox on a Lion system? I'm using Xcode 4.4.1 but I'd like to hear from a 4.3 install too.

Worked for me on Lion, but with 4.4.1 too, sorry and thanks for the fix.

comment:16 in reply to:  14 ; Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: closedreopened

Replying to and.damore@…:

I received buildbot failure reports from both lion buildbot and snowleopard buildbot, although with different errors.

I can confirm the Snow Leopard build failure (although oldest_supported_SDK gets set to 10.5, it somehow tries to use the nonexistent 10.7 SDK) on my Snow Leopard test machine with Xcode 3.2.6. I can confirm the Lion build failure (it can't find OpenSSL) on my Lion test machine with Xcode 4.3.3.

comment:17 in reply to:  16 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: edhem.bajric@… added

Replying to ryandesign@…:

I can confirm the Snow Leopard build failure (although oldest_supported_SDK gets set to 10.5, it somehow tries to use the nonexistent 10.7 SDK) on my Snow Leopard test machine with Xcode 3.2.6.

Has duplicate #36020.

comment:18 Changed 12 years ago by royliu@…

Does r97647 fix the problem? I added detection of Xcode >= 4.1.

Changed 12 years ago by pixilla (Bradley Giesbrecht)

Use "xcode-select -print-path" in place of hardcoded /Developer.

comment:19 Changed 12 years ago by pixilla (Bradley Giesbrecht)

On my system configures hardcoded /Developer path is a problem.

comment:20 Changed 12 years ago by chris.perl@…

My system is the same as pixilla. The hard coded paths to /Developer were causing a problem for me. Patching patch-configure.diff with patch-emulators-virtualbox-find-sdk.diff​ has allowed me to build virtualbox on my lion 10.7.4 system with xcode 4.4.1.

comment:21 Changed 12 years ago by royliu@…

Resolution: fixed
Status: reopenedclosed

Patch committed in r97817. I'm closing the ticket now. Will reopen the problems continue.

comment:22 Changed 12 years ago by royliu@…

Resolution: fixed
Status: closedreopened

comment:23 Changed 12 years ago by royliu@…

Well, it looks like the buildbot is still failing. Any ideas? What version of Mac OS X/Xcode is it running?

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

Last I heard, the Lion buildbot was running Xcode 4.3.2, and the Snow Leopard buildbot was running Xcode 3.2.6.

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

The version of clang in Xcode 4.3 does not honor the LIBRARY_PATH environment variable like newer versions of clang (and all versions of gcc that we've been using) do. So perhaps it's just a matter of getting the right -L flag in there.

comment:26 Changed 11 years ago by nxwolverine@…

Hi all,

I'm also having issues with getting Virtualbox 4.2.6 installed. My MacPorts is up-to-date (2.1.3). I'm running Mac OS X 10.6.8, with XCode 4.0.2.

When I run the installation I get the same error as previously reported:

Error: org.macports.configure for port virtualbox returned: configure failure: command execution failed
Please see the log file for port virtualbox for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port virtualbox failed

The log file report is:

:msg:main --->  Computing dependencies for virtualbox:info:main .:debug:main virtualbox has no conflicts
:debug:main Searching for dependency: pkgconfig
:debug:main Found Dependency: receipt exists for pkgconfig
:debug:main Searching for dependency: qt4-mac
:debug:main Found Dependency: receipt exists for qt4-mac
:debug:main Searching for dependency: curl
:debug:main Found Dependency: receipt exists for curl
:debug:main Searching for dependency: libidl
:debug:main Found Dependency: receipt exists for libidl
:debug:main Searching for dependency: libxml2
:debug:main Found Dependency: receipt exists for libxml2
:debug:main Searching for dependency: libxslt
:debug:main Found Dependency: receipt exists for libxslt
:debug:main Searching for dependency: openssl
:debug:main Found Dependency: receipt exists for openssl
:debug:main Searching for dependency: libsdl
:debug:main Found Dependency: receipt exists for libsdl
:debug:main Searching for dependency: vde2
:debug:main Found Dependency: receipt exists for vde2
:debug:main Searching for dependency: LibVNCServer
:debug:main Found Dependency: receipt exists for LibVNCServer
:msg:main
:debug:main Executing org.macports.main (virtualbox)
:debug:main changing euid/egid - current euid: 0 - current egid: 0:debug:main egid changed to: 501:debug:main euid changed to: 503:debug:main Skipping completed org.macports.archivefetch (virtualbox)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.fetch (virtualbox)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.checksum (virtualbox)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.extract (virtualbox)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:main Skipping completed org.macports.patch (virtualbox)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:configure configure phase started at Wed Feb  6 08:03:00 PST 2013
:notice:configure --->  Configuring virtualbox
:debug:configure Using compiler 'Mac OS X gcc 4.2'
:debug:configure Executing org.macports.configure (virtualbox)
:debug:configure Environment: CPATH='/opt/local/include' CFLAGS='-pipe -O2 -arch i386' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-pipe -O2 -arch i386' LIBRARY_PATH='/opt/local/lib' MACOSX_DEPLOYMENT_TARGET='10
.6' PKG_CONFIG_PATH='/opt/local/lib/pkgconfig' CXX='/usr/bin/g++-4.2' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/
virtualbox/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m32' LDFLAGS='-L/opt/local/lib -arch i386' FCFLAGS='-pipe -O2 -m32' OBJC='/usr/bin/gcc-4.2' INSTALL='/usr/bin/install -c' MOC='/opt/local/bin/moc' QMAKES
PEC='macx-g++' FFLAGS='-pipe -O2 -m32' OBJCFLAGS='-pipe -O2 -arch i386' QTDIR='/opt/local' CC_PRINT_OPTIONS='YES' CC='/usr/bin/gcc-4.2' QMAKE='/opt/local/bin/qmake'
:debug:configure Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.6" && ./configure --w
ith-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/usr/bin/gcc-4.2 --with-g++=/usr/bin/g++-4.2 --enable-vde --enable-vnc'
:debug:configure Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.6" && ./configur
e --with-qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/usr/bin/gcc-4.2 --with-g++=/usr/bin/g++-4.2 --enable-vde --enable-vnc
:info:configure Checking for environment: Determined build machine: darwin.x86, target machine: darwin.x86, OK.
:info:configure Checking for kBuild: found, OK.
:info:configure Checking for Darwin version: found version 10.6 (SDK: /Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.5.sdk), OK.
:info:configure Checking for gcc: found version 4.2.1, OK.
:info:configure Checking for Open Watcom:
:info:configure   ** Open Watcom was not found!
:info:configure Checking for libIDL: found version 0.8.14, OK.
:info:configure Checking for ssl:
:info:configure   libcrypto not found at -I/opt/local/include /opt/local/lib/libcrypto.dylib /opt/local/lib/libssl.dylib or openssl headers not found
:info:configure   Check the file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.6/configure.log for detailed 
error information.
:info:configure Check /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.6/configure.log for details
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/work/VirtualBox-4.2.6" && ./configure --with-
qt-dir=/opt/local --with-openssl-dir=/opt/local --with-gcc=/usr/bin/gcc-4.2 --with-g++=/usr/bin/g++-4.2 --enable-vde --enable-vnc
:info:configure Exit code: 1
:error:configure org.macports.configure for port virtualbox returned: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
    while executing
"$procedure $targetname"
:info:configure Warning: targets not executed for virtualbox: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install
:notice:configure Please see the log file for port virtualbox for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/main.log

Any ideas on how to get Virtualbox to install? If my combo of Mac OS X and XCode not supported?

Thanks in advance,

Kartik

Version 2, edited 11 years ago by nxwolverine@… (previous) (next) (diff)

comment:27 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: nxwolverine@… added

@nxwolverine, as stated above, the version of clang in Xcode 4.3 (and earlier) does not support LIBRARY_PATH, and therefore, because the virtualbox build system has apparently not been programmed to use the correct -L flags, it cannot find the libraries it needs.

The workaround for those using Xcode 4.0 through 4.2 inclusive would be to force the use of the gcc-4.2 compiler:

sudo port clean virtualbox
sudo port install virtualbox configure.compiler=gcc-4.2

The workaround for those using Xcode 4.3.x (since it does not include gcc-4.2) would be to install the apple-gcc42 port and use that:

sudo port clean virtualbox
sudo port install apple-gcc42
sudo port install virtualbox configure.compiler=apple-gcc-4.2

Users of Xcode 4.4 and later are not affected because the included version of clang supports LIBRARY_PATH. Users of Xcode 3.x are not affected because on those versions of Xcode MacPorts will automatically use gcc and not clang.

comment:28 in reply to:  27 ; Changed 11 years ago by nxwolverine@…

Replying to ryandesign@…:

Thanks for the explanation.

I tried out the XCode 4.0 - 4.2 tip you suggested, and the installation still fails. This time though, it's getting to the point of extracting Virtualbox.

I'm suspecting that it's because I didn't do a full clean of all of the dependencies from the initial install? Is this required?

Thanks!

Kartik

comment:29 in reply to:  28 ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to nxwolverine@…:

I tried out the XCode 4.0 - 4.2 tip you suggested, and the installation still fails. This time though, it's getting to the point of extracting Virtualbox.

I'm not sure what went wrong. Could you attach the main.log file?

Changed 11 years ago by nxwolverine@…

Attachment: main.2.log added

Log file cataloguing problem installing Virtualbox on Mac OS X 10.6.8 with XCode 4.0.2

comment:30 in reply to:  29 Changed 11 years ago by nxwolverine@…

Replying to ryandesign@…:

Replying to nxwolverine@…:

I tried out the XCode 4.0 - 4.2 tip you suggested, and the installation still fails. This time though, it's getting to the point of extracting Virtualbox.

I'm not sure what went wrong. Could you attach the main.log file?

So I run the clean command successfully, and then proceed with the install, using the explicit argument calling the GCC 4.2 compiler. The initial output I get looks promising:

--->  Computing dependencies for virtualbox
--->  Fetching archive for virtualbox
--->  Attempting to fetch virtualbox-4.2.6_0+vde2+vnc.darwin_10.i386.tbz2 from http://packages.macports.org/virtualbox
--->  Attempting to fetch virtualbox-4.2.6_0+vde2+vnc.darwin_10.i386.tbz2 from http://lil.fr.packages.macports.org/virtualbox
--->  Attempting to fetch virtualbox-4.2.6_0+vde2+vnc.darwin_10.i386.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/virtualbox
--->  Fetching distfiles for virtualbox
--->  Verifying checksum(s) for virtualbox
--->  Extracting virtualbox
--->  Applying patches to virtualbox
--->  Configuring virtualbox

And then it spits out the following error:

Error: org.macports.configure for port virtualbox returned: configure failure: command execution failed
Please see the log file for port virtualbox for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulators_virtualbox/virtualbox/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port virtualbox failed

I've attached the main.log file. Hope that helps to diagnose the problem.

Thanks for your help!

Kartik

comment:31 Changed 10 years ago by whcordis@…

Cc: whcordis@… added

Cc Me!

Changed 10 years ago by whcordis@…

Attachment: main.3.log added

Build Log detailing failure of build on OS X 10.8.5 with XCode 5.0

comment:32 Changed 10 years ago by whcordis@…

This problem has reappeared for me on OS X 10.8.5 with XCode 5.0. I've attached the log for review.

comment:33 Changed 10 years ago by mallman (Michael Allman)

This port is broken on systems with Xcode 5 because Xcode 5 doesn't come with OSX 10.7 SDK.

comment:34 Changed 10 years ago by mail@…

I also get this issue after uninstalling my installed (and working) virtualbox 4.2.16 and trying to reinstall.

OSX 10.8.5, latest XCode (5.0.2) is installed in /Applications/Xcode.app/Contents/Developer

comment:35 Changed 10 years ago by jiri.tyr@…

Cc: jiri.tyr@… added

Cc Me!

comment:36 Changed 10 years ago by jiri.tyr@…

Cc: jiri.tyr@… removed

Cc Me!

comment:37 Changed 10 years ago by jiri.tyr@…

Cc: jiri.tyr@… added

Cc Me!

comment:38 Changed 10 years ago by gamperl@…

Cc: gamperl@… added

Cc Me!

comment:39 Changed 10 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:40 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: kprussing74@… iamsudo@… added

Has duplicates #40619, #50621.

comment:41 Changed 4 years ago by chrstphrchvz (Christopher Chavez)

Resolution: fixed
Status: reopenedclosed

In 80709efdc0b4154e6c0b26d01a28d9bae04850a9/macports-ports (master):

virtualbox: delete port

Port has not been successfully updated in 7 years, has reported build
problems, has broken dependencies (vde2), and is unbuildable on recent
macOS versions (requires apple-gcc42).

Closes: #35808
Closes: #36927
Closes: #38364
Closes: #38558
Closes: #50622
Closes: #51999

Note: See TracTickets for help on using tickets.