#48694 closed defect (duplicate)
boost @1.59.0_0 does not install on PPC Leopard, Mac OS X 10.5.8, because of missing utility lbzip2
| Reported by: | ballapete (Peter "Pete" Dyballa) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | Cc: | ||
| Port: | boost |
Description
The builds ends with
...failed updating 1 target... ...skipped 1 target... ...updated 526 targets... Command failed: cd "/opt/local/var/macports/build/_opt_mports_trunk_dports_devel_boost/boost/work/boost_1_59_0" && /opt/local/var/macports/build/_opt_mports_trunk_dports_devel_boost/boost/work/boost_1_59_0/b2 -d2 --layout=tagged --debug-configuration --user-config=user-config.jam -sBZIP2_INCLUDE=/opt/local/include -sBZIP2_LIBPATH=/opt/local/lib -sEXPAT_INCLUDE=/opt/local/include -sEXPAT_LIBPATH=/opt/local/lib -sZLIB_INCLUDE=/opt/local/include -sZLIB_LIBPATH=/opt/local/lib -sICU_PATH=/opt/local variant=release -j1 architecture=power address-model=32 --disable-long-double link=shared threading=multi Exit code: 1
but it's actually this, a few lines below, that names the cause:
DEBUG: Failed to locate 'lbzip2' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it?
Although it's useless to install a parallel bzip2 on a 7447A CPU I have started port install lbzip2…
Attachments (1)
Change History (4)
Changed 9 years ago by ballapete (Peter "Pete" Dyballa)
comment:1 Changed 9 years ago by mf2k (Frank Schima)
| Cc: | ryandesign@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to ryandesign@… |
comment:2 follow-up: 3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Replying to Peter_Dyballa@…:
The builds ends with
...failed updating 1 target... ...skipped 1 target... ...updated 526 targets... Command failed: cd "/opt/local/var/macports/build/_opt_mports_trunk_dports_devel_boost/boost/work/boost_1_59_0" && /opt/local/var/macports/build/_opt_mports_trunk_dports_devel_boost/boost/work/boost_1_59_0/b2 -d2 --layout=tagged --debug-configuration --user-config=user-config.jam -sBZIP2_INCLUDE=/opt/local/include -sBZIP2_LIBPATH=/opt/local/lib -sEXPAT_INCLUDE=/opt/local/include -sEXPAT_LIBPATH=/opt/local/lib -sZLIB_INCLUDE=/opt/local/include -sZLIB_LIBPATH=/opt/local/lib -sICU_PATH=/opt/local variant=release -j1 architecture=power address-model=32 --disable-long-double link=shared threading=multi Exit code: 1
This is a duplicate of #48684.
but it's actually this, a few lines below, that names the cause:
DEBUG: Failed to locate 'lbzip2' in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its MacPorts configuration time location, did you move it?
The log you attached doesn't contain that line. But if you did see that line in another attempt, I believe it is caused by a longstanding but hard-to-diagnose MacPorts base bug that causes it to print an incorrect error message sometimes when builds fail.
Although it's useless to install a parallel bzip2 on a 7447A CPU I have started
port install lbzip2…
You're correct that if you have a single-core machine, there is no benefit to installing a parallel bzip2 implementation such as lbzip2 or pbzip2. MacPorts automatically uses these if found, to help users of multi-core machines, but is happy to use the single-threaded bzip2 program included with OS X if you don't have them installed.
comment:3 Changed 9 years ago by ballapete (Peter "Pete" Dyballa)
Replying to ryandesign@…:
Replying to Peter_Dyballa@…:
This is a duplicate of #48684.
You're correct that if you have a single-core machine, there is no benefit to installing a parallel bzip2 implementation such as lbzip2 or pbzip2. MacPorts automatically uses these if found, to help users of multi-core machines, but is happy to use the single-threaded bzip2 program included with OS X if you don't have them installed.
In that case this ticket can be closed. Obviously the build stops with the same error that has been reported before in #48684.
main.log