#14687: BUG: destroot and (build && destroot) yield different results ----------------------------------------+----------------------------------- Reporter: marcuscalhounlopez@mac.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: ports | Version: 1.6.0 Keywords: | ----------------------------------------+----------------------------------- As has been discussed #13948, mzscheme * Fails with "port destroot mzscheme" * Succeeds with "port build mzscheme && port destroot mzscheme" The error is: {{{ find-executable-path: expected argument of type <path or string (sans nul)>; given "" }}} Similarly, when the boost port contains {{{ build.env BZIP2_INCLUDE=${prefix}/include BZIP2_LIBPATH=${prefix}/lib \ ZLIB_INCLUDE=${prefix}/include ZLIB_LIBPATH=${prefix}/lib }}} then boost * Fails with "port destroot boost" * Succeeds with "port build boost && port destroot boost" The error is: {{{ /opt/local/var/macports/build/_Users_macports_MacPorts_mports_devel_boost/work/boost_1_34_1/tools/build/v2/util/path.jam:465: in make-UNIX from module path error: Empty path passed to 'make-UNIX' }}} Strangely enough, a fix (for boost but not for mzscheme) is to simply add {{{ destroot.env ${build.env} }}} I assume this was the reason for the boost rollback r34913. Since both errors involve empty paths, and each has at lest one common workaround,[[BR]] I thought they might be symptom of a common bug.[[BR]] I am using MP 1.600 on Leopard. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14687> MacPorts </projects/macports> Ports system for Mac OS