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?

[porchy13]

On macOS High Sierra, the compilation of osxfuse fails due to the lack of lbzip2. After manually install lbzip2, osxfuse does not complaint anymore about lbzip2.

[porchy13]

log of the compilation process

[porchy13]

Sorry for the forget: the title should be osxfuse @3.7.1

[ryandesign (Ryan Carsten Schmidt)]

No, that is not correct. osxfuse has no need for lbzip2. MacPorts base can optionally use lbzip2 if present. It is not a problem if lbzip2 is not present. It is a bug that MacPorts base is printing this error.

[jmroot (Joshua Root)]

Unless the lbzip2 port is installed and the executable really has been removed.

[ryandesign (Ryan Carsten Schmidt)]

Replying to jmroot:

Unless the lbzip2 port is installed and the executable really has been removed.

Which is almost certainly not the case. Tons of users have reported this erroneous error message. (#46231, #48694, #54167, #54267.) MacPorts clearly has a bug where it neglects to clear out an irrelevant error message before displaying it to the user.

[raimue (Rainer Müller)]

In 113ef219df4f0cf920ae61dc14a7bea469e1148e/macports-base:

mportexec: Remove misleading errorInfo output

The port target was evaluated in a separate Tcl slave interpreter, which
depending on the way it exits, does not necessarily update $::errorInfo
of the master interpreter. Therefore $::errorInfo in the master
interpreter often contains unrelated error information which leads to
confusion in the log file and caused tickets to be filed with the wrong
information.

All error information related to the failure should have already been
emitted by the slave interpreter.

Closes: #55560

[raimue (Rainer Müller)]

In 0ebdf20e8a82ae45422a9ed6bea106f9381992d5/macports-base:

mportexec: Remove misleading errorInfo output

The port target was evaluated in a separate Tcl slave interpreter, which
depending on the way it exits, does not necessarily update $::errorInfo
of the master interpreter. Therefore $::errorInfo in the master
interpreter often contains unrelated error information which leads to
confusion in the log file and caused tickets to be filed with the wrong
information.

All error information related to the failure should have already been
emitted by the slave interpreter.

Closes: #55560
(cherry picked from commit 113ef219df4f0cf920ae61dc14a7bea469e1148e)