Yes, there was a log file. Here is the last bit of a long file:
:info:build Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_ma
cports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/w
ork/gettext-0.19.5" && /usr/bin/make -j4 -w all
:info:build Exit code: 2
:error:build org.macports.build for port gettext returned: command
execution fai
led
:debug:build Error code: CHILDSTATUS 19793 2
:debug:build Backtrace: command execution failed
while executing
"system -nice 0 $fullcmdstring"
("eval" body line 1)
invoked from within
"eval system $notty $nice \$fullcmdstring"
invoked from within
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"portbuild::build_main org.macports.build"
("eval" body line 1)
invoked from within
"eval $procedure $targetname"
:info:build Warning: targets not executed for gettext:
org.macports.install org.
macports.build org.macports.destroot
On Fri, 7 Aug 2015, Chris Jones wrote:
On 07/08/15 13:30, - wrote:
For some days now any port action that calls for gettext bombs. Here is
one part of the result:
Error: org.macports.build for port gettext returned: command execution
failed
Any thoughts?
Yes. Is that all that was posted, or was a log file mentioned by chance ??
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
XB
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
