Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#55560 closed defect (fixed)

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?

Reported by: porchy13 Owned by: raimue (Rainer Müller)
Priority: Normal Milestone: MacPorts 2.4.3
Component: base Version: 2.4.2
Keywords: Cc:
Port:

Description

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.

Attachments (1)

main.log (3.2 MB) - added by porchy13 4 years ago.
log of the compilation process

Change History (8)

Changed 4 years ago by porchy13

Attachment: main.log added

log of the compilation process

comment:1 Changed 4 years ago by porchy13

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

comment:2 Changed 4 years ago by ryandesign (Ryan Schmidt)

Component: portsbase
Keywords: osxfuse lbzip2 removed
Port: osxfuse removed
Summary: osxfuse needs a dependence on lbzip2Failed 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?

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.

comment:3 Changed 4 years ago by jmroot (Joshua Root)

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

comment:4 in reply to:  3 Changed 4 years ago by ryandesign (Ryan 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.

comment:5 Changed 4 years ago by raimue (Rainer Müller)

Owner: set to raimue
Resolution: fixed
Status: newclosed

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

comment:6 Changed 4 years ago by 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)

comment:7 Changed 4 years ago by raimue (Rainer Müller)

Milestone: MacPorts 2.4.3
Note: See TracTickets for help on using tickets.