Error: build org.macports.build for port gettext returned: command execution failed

[wolfhard.langer@…]

Hello,

MacPort with Version 2.3.1 is installed on my iMac (Mavericks, 10.9.4). Xcode is installed and has version 5.1.1. The command line developer tools have been installed.

The command "sudo port upgrade outdated" is not successful for "gettext-0.19.2-x86_64":

Output from the main.log:

...
:info:configure checking that generated files are newer than configure... done
:info:configure configure: creating ./config.status
:info:configure config.status: creating Makefile
:info:configure config.status: creating installpaths
:info:configure config.status: creating po/Makefile
:info:configure config.status: executing po-directories commands
:debug:configure Privilege de-escalation not attempted as not running as root.
:debug:build build phase started at Sun Aug  3 15:23:53 CEST 2014
:notice:build --->  Building gettext
:debug:build Executing org.macports.build (gettext)
:info:build --->  Building gettext for architecture x86_64
:debug:build Environment: 
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/.CC_PRINT_OPTIONS'
CPATH='/opt/local/include'
LIBRARY_PATH='/opt/local/lib'
MACOSX_DEPLOYMENT_TARGET='10.9'
:debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64" && /usr/bin/make -j4 -w all'
:debug:build Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64" && /usr/bin/make -j4 -w all 
:info:build make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64'
:info:build CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing autoconf
:info:build  cd . && /bin/sh /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing automake-1.13 --gnu
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing: '''line 81: automake-1.13: command not found'''
:info:build WARNING: 'automake-1.13' is missing on your system.
:info:build          You should only need it if you modified 'Makefile.am' or
:info:build          'configure.ac' or m4 files included by 'configure.ac'.
:info:build          The 'automake' program is part of the GNU Automake package:
:info:build          <http://www.gnu.org/software/automake>
:info:build          It also requires GNU Autoconf, GNU m4 and Perl in order to run:
:info:build          <http://www.gnu.org/software/autoconf>
:info:build          <http://www.gnu.org/software/m4/>
:info:build          <http://www.perl.org/>
:info:build make: *** [Makefile.in] Error 1
:info:build make: *** Waiting for unfinished jobs....
:info:build sh: build-aux/git-version-gen: No such file or directory
:info:build configure.ac:25: error: AC_INIT should be called with package and version arguments
:info:build aclocal.m4:151: AM_INIT_AUTOMAKE is expanded from...
:info:build configure.ac:25: the top level
:info:build autom4te: /opt/local/bin/gm4 failed with exit status: 1
:info:build make: *** [configure] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64" && /usr/bin/make -j4 -w all 
:info:build Exit code: 2
:error:build org.macports.build for port gettext returned: command execution failed
:debug:build Error code: NONE
:debug:build Backtrace: command execution failed
    while executing
"proc-org.macports.build-build-0 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
:notice:build Please see the log file for port gettext for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/main.log

After this the command "sudo port clean gettext" has been started but the command "sudo port upgrade gettext" too was not successful.

I would like to ask you whether you could give me a hint so that the upgrade of gettext would be possible.

Thank you.

[wolfhard.langer@…]

Log-Datei for upgrade of gettext

[neverpanic (Clemens Lang)]

Please use WikiFormatting and preview your post when posting in Trac. When filing tickets for ports, please fill in the port field and Cc the maintainer if any (port info --maintainer gettext).

There seems to be a problem with the file timestamps on your system. Are you using an uncommon filesystem or is your system clock off?

[neverpanic (Clemens Lang)]

Ryan: Did you check the +universal build? This seems to be a problem that might be caused by the separate build root. Do we preserve file timestamps while copying the build root?

[wolfhard.langer@…]

Hello, thank you for correcting my ticket entries and for your hints and sorry for not using WikiFormatting. On my iMac there is a standard filesystem and the clock is running on the iMac. During installation of XCode or MacPorts I do not remember error messages. Also the command "sudo port selfupdate" did not show an error.

[ryandesign (Ryan Carsten Schmidt)]

Sorry; I did not see this ticket until now. I have built all ports universal on my main machine for years and I don't recall any problem with gettext in recent years. I will have to compare your log with mine to see what's different.

[ryandesign (Ryan Carsten Schmidt)]

Replying to cal@…:

There seems to be a problem with the file timestamps on your system.

What makes you say that?

[neverpanic (Clemens Lang)]

:info:build WARNING: 'automake-1.13' is missing on your system.
:info:build          You should only need it if you modified 'Makefile.am' or
:info:build          'configure.ac' or m4 files included by 'configure.ac'.

But the port doesn't modify Makefile.am, configure.ac or any other m4 files. It only patches ltmain.sh. So either, the timestamps of the files are wrong on extraction (which we should, however, notice in a non-universal build), or somehow the x86_64 version of the source tree has corrupted/incorrect timestamps.

[ryandesign (Ryan Carsten Schmidt)]

Wolfhard, I don't suppose you've modified the gettext portfile in any way?

[wolfhard.langer@…]

Replying to ryandesign@…:

Wolfhard, I don't suppose you've modified the gettext portfile in any way?

Thank you very much for taking care on my ticket. During the installation of MacPorts on my iMac I used the documentation and worked on it step by step. And I did not modify the gettext portfile or other files.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

I will have to compare your log with mine to see what's different.

I didn't see any applicable differences between your log and mine, until the point where it fails. The only difference in the configure phase is that you have java installed and I don't.

Your disk isn't formatted case-sensitive by chance is it? Mine is case-insensitive, the OS X default. However we use case-sensitive filesystems on the buildbot too so it shouldn't be a problem.

Is your disk very fast—an SSD perhaps? If there is a timing problem (where doing one operation within the same second as another operation might cause a problem) a fast disk would make that more likely.

Parallel building also adds some randomness and uncertainty to the build. It hasn't been a problem for gettext before, but for easier debugging, we could disable parallel building temporariliy.

You could try running:

sudo port clean gettext
sudo port upgrade gettext build.jobs=1

a few more times. See if it fails with the same automake error in the log each time.

[wolfhard.langer@…]

Replying to ryandesign@…:

Replying to ryandesign@…: You could try running:

sudo port clean gettext
sudo port upgrade gettext build.jobs=1

a few more times. See if it fails with the same automake error in the log each time.

The disc on my iMac from midst 2010 is also OS X default, it not has been formatted by me. Also there is no SSD in use.

The two commands have been repeated three times and the result is different from the entries with which this ticket has been opened. In all three trials the last 29 lines are the same:

:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing: line 81: aclocal-1.13: command not found
:info:build WARNING: 'aclocal-1.13' is missing on your system.
:info:build          You should only need it if you modified 'acinclude.m4' or
:info:build          'configure.ac' or m4 files included by 'configure.ac'.
:info:build          The 'aclocal' program is part of the GNU Automake package:
:info:build          <http://www.gnu.org/software/automake>
:info:build          It also requires GNU Autoconf, GNU m4 and Perl in order to run:
:info:build          <http://www.gnu.org/software/autoconf>
:info:build          <http://www.gnu.org/software/m4/>
:info:build          <http://www.perl.org/>
:info:build make[2]: *** [aclocal.m4] Error 127
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/gettext-runtime'
:info:build make[1]: *** [all-recursive] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64" && /usr/bin/make -w all 
:info:build Exit code: 2
:error:build org.macports.build for port gettext returned: command execution failed
:debug:build Error code: NONE
:debug:build Backtrace: command execution failed
    while executing
"proc-org.macports.build-build-0 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
:notice:build Please see the log file for port gettext for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/main.log

[wolfhard.langer@…]

Hello,

the port gettext and its dependencies have been uninstalled and then I tried to install the port gettex (sudo port -t -v install gettext) but without success this means again "proc-org.macports.build-build-0 org.macports.build" failed:

config.status: creating po/Makefile
=== configuring in examples (/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-i386/gettext-tools/examples)
configure: running /bin/sh ./configure --disable-option-checking '--prefix=/opt/local'  'ac_cv_prog_AWK=/usr/bin/awk' 'ac_cv_path_GREP=/usr/bin/grep' 'ac_cv_path_SED=/usr/bin/sed' '--disable-csharp' '--disable-native-java' '--disable-openmp' '--without-emacs' '--with-included-gettext' '--with-included-glib' '--with-included-libcroco' '--with-included-libunistring' '--with-included-libxml' '--without-cvs' '--without-git' '--without-xz' '--disable-dependency-tracking' 'CC=/usr/bin/clang' 'CFLAGS=-pipe -Os -arch i386' 'LDFLAGS=-L/opt/local/lib -Wl,-headerpad_max_install_names -arch i386' 'CPPFLAGS=-no-cpp-precomp' 'CXX=/usr/bin/clang++' 'CXXFLAGS=-pipe -Os -arch i386 -stdlib=libc++' --cache-file=/dev/null --srcdir=.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ../../build-aux/install-sh -c -d
checking for gawk... (cached) /usr/bin/awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for a sed that does not truncate output... (cached) /usr/bin/sed
checking whether NLS is requested... yes
checking for msgfmt... no
checking for gmsgfmt... :
checking for xgettext... no
checking for msgmerge... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating installpaths
config.status: creating po/Makefile
config.status: executing po-directories commands
Warning: An activity was attempted outside sandbox: /.attbin/uname
Warning: An activity was attempted outside sandbox: /AppleInternal
Warning: An activity was attempted outside sandbox: /AppleInternal/Developer/Toolchains
Warning: An activity was attempted outside sandbox: /Developer
Warning: An activity was attempted outside sandbox: /Info.plist
Warning: An activity was attempted outside sandbox: /Network/Library/Java/Extensions
Warning: An activity was attempted outside sandbox: /bin;/bin/sh
Warning: An activity was attempted outside sandbox: /non/exist/ent
Warning: An activity was attempted outside sandbox: /opt/local/bin/bzip2
Warning: An activity was attempted outside sandbox: /opt/sfw/bin/gmkdir
Warning: An activity was attempted outside sandbox: /opt/sfw/bin/mkdir
Warning: An activity was attempted outside sandbox: /var/mail/macports
--->  Building gettext
--->  Building gettext for architecture x86_64
make: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing autoconf
 cd . && /bin/sh /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing automake-1.13 --gnu
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing: line 81: automake-1.13: command not found
WARNING: 'automake-1.13' is missing on your system.
         You should only need it if you modified 'Makefile.am' or
         'configure.ac' or m4 files included by 'configure.ac'.
         The 'automake' program is part of the GNU Automake package:
         <http://www.gnu.org/software/automake>
         It also requires GNU Autoconf, GNU m4 and Perl in order to run:
         <http://www.gnu.org/software/autoconf>
         <http://www.gnu.org/software/m4/>
         <http://www.perl.org/>
make: *** [Makefile.in] Error 1
make: *** Waiting for unfinished jobs....
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64/build-aux/missing: line 81: autoconf: command not found
WARNING: 'autoconf' is missing on your system.
         You should only need it if you modified 'configure.ac',
         or m4 files included by it.
         The 'autoconf' program is part of the GNU Autoconf package:
         <http://www.gnu.org/software/autoconf/>
         It also requires GNU m4 and Perl in order to run:
         <http://www.gnu.org/software/m4/>
         <http://www.perl.org/>
make: *** [configure] Error 127
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64'
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.2-x86_64" && /usr/bin/make -j4 -w all 
Exit code: 2
Error: org.macports.build for port gettext returned: command execution failed
Warning: targets not executed for gettext: org.macports.activate org.macports.build org.macports.destroot org.macports.install
Please see the log file for port gettext for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port gettext failed

I would like to ask you for your support to solve this problem during installation of the port gettext.

Thank you.

[wolfhard.langer@…]

Hello,

after using the commands mentioned in ticket #40463 (sudo port clean gettext; sudo port -d configure gettext -universal) the command sudo port -d install gettext -universal had function and also sudo port -d upgrade outdated had function:

$ sudo port -d outdated
DEBUG: Copying /Users/user/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
No installed ports are outdated.
$ 

Probably this ticket can be closed.

Thank you.

[ryandesign (Ryan Carsten Schmidt)]

So, with the above commands, you've replaced your universal build of gettext with a nonuniversal build of gettext. If you have no other ports installed with universal variants that depend on gettext, that's fine, but if you do, those other ports may now be broken. Run "sudo port -v rev-upgrade" to determine if that's the case; if anything is broken, MacPorts will try to rebuild it. If the port that's broken is installed universal and depends on gettext, then that would involve MacPorts trying to rebuild gettext universal again, which will probably fail again as you experienced before.

We haven't yet figured out why the build is failing on your system, but I'm now suspicious of some of the lines you showed above, specifically:

Warning: An activity was attempted outside sandbox: /.attbin/uname
Warning: An activity was attempted outside sandbox: /AppleInternal
Warning: An activity was attempted outside sandbox: /AppleInternal/Developer/Toolchains
Warning: An activity was attempted outside sandbox: /Developer
Warning: An activity was attempted outside sandbox: /Info.plist
Warning: An activity was attempted outside sandbox: /Network/Library/Java/Extensions
Warning: An activity was attempted outside sandbox: /bin;/bin/sh
Warning: An activity was attempted outside sandbox: /non/exist/ent
Warning: An activity was attempted outside sandbox: /opt/local/bin/bzip2
Warning: An activity was attempted outside sandbox: /opt/sfw/bin/gmkdir
Warning: An activity was attempted outside sandbox: /opt/sfw/bin/mkdir
Warning: An activity was attempted outside sandbox: /var/mail/macports

What's /AppleInternal? I'm wondering if this indicates the use of any pre-release versions of Apple software, perhaps even Xcode or its command line tools, which might explain the problem. What's /opt/sfw? I'm concerned that software located there may be interfering with MacPorts building your requested ports.

[ryandesign (Ryan Carsten Schmidt)]

Cc Me!

[wolfhard.langer@…]

Here ist the result of the command "sudo port -v rev-upgrade":

$ sudo port -v rev-upgrade
--->  Scanning binaries for linking errors
--->  No broken files found.

$ sudo port info gettext
gettext @0.19.2 (devel)
Variants:             (+)universal
Description:          gettext is the GNU internationalization (i18n) and localization (l10n) library, used for writing multilingual programs.
Homepage:             http://www.gnu.org/software/gettext/
Library Dependencies: expat, libiconv, ncurses
Platforms:            darwin, freebsd, linux
License:              LGPL-2.1+ GPL-3+
Maintainers:          ryandesign@macports.org

In ticket:43886 the string "/AppleInternal" also can be found. And the string "/opt/sfw" can be found in ticket:43947. I would like to ask you if you could check if eventually the contents in ticket:43947 is related to my ticket?

Thank you.

[ryandesign (Ryan Carsten Schmidt)]

Replying to wolfhard.langer@…:

Here ist the result of the command "sudo port -v rev-upgrade":

$ sudo port -v rev-upgrade
--->  Scanning binaries for linking errors
--->  No broken files found.

Ok good, nothing is broken.

$ sudo port info gettext
gettext @0.19.2 (devel)
Variants:             (+)universal
Description:          gettext is the GNU internationalization (i18n) and localization (l10n) library, used for writing multilingual programs.
Homepage:             http://www.gnu.org/software/gettext/
Library Dependencies: expat, libiconv, ncurses
Platforms:            darwin, freebsd, linux
License:              LGPL-2.1+ GPL-3+
Maintainers:          ryandesign@macports.org

The interesting information here is that the universal variant is being enabled by default, presumably because you inserted "+universal" into your variants.conf file. If you don't actually need universal builds, you could remove that. Non-universal builds are faster and take less disk space. Also, you'll be more likely to be able to get binaries from our server, which should be much faster than building ports yourself.

In ticket:43886 the string "/AppleInternal" also can be found. And the string "/opt/sfw" can be found in ticket:43947.

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").

I would like to ask you if you could check if eventually the contents in ticket:43947 is related to my ticket?

I don't see any similarities to your situation.

[neverpanic (Clemens Lang)]

Hi,

Replying to 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.

[wolfhard.langer@…]

Replying to ryandesign@…:

The interesting information here is that the universal variant is being enabled by default, presumably because you inserted "+universal" into your variants.conf file. If you don't actually need universal builds, you could remove that. Non-universal builds are faster and take less disk space. Also, you'll be more likely to be able to get binaries from our server, which should be much faster than building ports yourself.

Thank you for your answers and for your hints. In variants.conf I removed the entry "+universal". After this a selfupdate has been done and outdated ports have been upgraded. Then the installation of digikam has been continued and it has been finished successfully (ticket:44992). It seems that macports works fine on my iMac.

Thank you for your support.

[ryandesign (Ryan Carsten Schmidt)]

I'm pleased you were able to install the desired ports non-universal. We still haven't explained why the build failed when building universal, but if you need that in the future, we can continue to look into it then.