bitcoin @0.8.1 +daemon: Should not set configure.cmd to qmake

[macports@…]

Build fails during configure phase when Qt is not installed:

--->  Configuring bitcoin
DEBUG: Using compiler 'Mac OS X gcc 4.2'
DEBUG: Executing org.macports.configure (bitcoin)
DEBUG: 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' CXX='/usr/bin/g++-4.2' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_finance_bitcoin/bitcoin/work/.CC_PRINT_OPTIONS' F90FLAGS='-pipe -O2 -m32' LDFLAGS='-L/opt/local/lib -arch i386' OBJC='/usr/bin/gcc-4.2' FCFLAGS='-pipe -O2 -m32' INSTALL='/usr/bin/install -c' OBJCFLAGS='-pipe -O2 -arch i386' FFLAGS='-pipe -O2 -m32' CC_PRINT_OPTIONS='YES' CC='/usr/bin/gcc-4.2'
DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_finance_bitcoin/bitcoin/work/bitcoin-0.8.1-linux/src" && qmake   '
DEBUG: Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_finance_bitcoin/bitcoin/work/bitcoin-0.8.1-linux/src" && qmake    
sh: qmake: command not found
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_finance_bitcoin/bitcoin/work/bitcoin-0.8.1-linux/src" && qmake    
Exit code: 127
Error: org.macports.configure for port bitcoin returned: configure failure: command execution failed

Adding set configure.cmd "true" in the variant definition allows the build to succeed. (Maybe there's a cleaner way to skip the configure phase. I know almost nothing about MacPorts.)

[cooljeanius (Eric Gallager)]

Maybe there's a cleaner way to skip the configure phase.

Yes, there is. It's: use_configure no

[larryv (Lawrence Velázquez)]

Be aware that setting use_configure no disables a lot of automatic behavior, like the implicit +universal variant. So it’s not something you can throw around lightly.

If the build does not require qmake, why does it currently claim to? Does bitcoin actually build correctly without running a configure phase?

[macports@…]

Replying to larryv@…:

If the build does not require qmake, why does it currently claim to? Does bitcoin actually build correctly without running a configure phase?

The build requires qmake if you're going to build the GUI, but if you're only building the daemon, then you do not need to run qmake. I am running the bitcoind that I built using the corrected port right now, and it's fully functional.

(By the way, 0.8.2 is out. The port builds it just fine, once you adjust the hashes.)

[cooljeanius (Eric Gallager)]

Cc Me!

[easye]

Fixed in r108486.