[MacPorts] #44528: Error: build org.macports.build for port gettext returned: command execution failed
MacPorts
noreply at macports.org
Sun Sep 14 12:46:39 PDT 2014
#44528: Error: build org.macports.build for port gettext returned: command
execution failed
--------------------------------+--------------------------
Reporter: wolfhard.langer@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.1
Resolution: | Keywords:
Port: gettext |
--------------------------------+--------------------------
Comment (by cal@…):
Hi,
Replying to [comment:16 ryandesign@…]:
> Hmm, ok. Do you actually have these paths on disk? If not, then we can
ignore it. I'm just not familiar with the behavior of trace mode ("`-t`").
You can ignore those paths. Sometimes (or rather, often?) autoconf scripts
access paths on disk that do not exist and/or never should. Trace mode in
its currently released state reports those back to the user in these
messages. Note that some of the paths in this list aren't supposed to
exist, e.g. `/non/exist/ent`.
The trunk version of trace mode hides sandbox violations for files that
don't actually exist from the warning output.
--
Ticket URL: <https://trac.macports.org/ticket/44528#comment:17>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list