#40463: gettext hangs during upgrade ------------------------------+-------------------------- Reporter: saschaschnepp@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: gettext | ------------------------------+-------------------------- Changes (by macsforever2000@…): * owner: macports-tickets@… => ryandesign@… Old description:

Hello,

I am trying to upgrade gettext on a 10.7.5 Lion with Macports 2.2.0. I read the tickets #34221 and #36740 but I think this is a different problem.

The upgrade got stuck during the configure stage and using -v -d I can see that the last item is the check for ranlib. This is the output of configure, please tell me if anyone requires more information.

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 gcc... /usr/bin/clang checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/clang accepts -g... yes checking for /usr/bin/clang option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... none checking for bison... bison -y checking whether to use Java... yes checking how to run the C preprocessor... /usr/bin/clang -E checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for Java compiler... javac -target 1.1 -source 1.3 checking for jar... jar checking for preferred C# implementation... no checking for C# compiler... no checking build system type... x86_64-apple-darwin11.4.2 checking host system type... x86_64-apple-darwin11.4.2 checking for Minix Amsterdam compiler... no checking for ar... ar checking for ranlib... ranlib

I would greatly appreciate help.

New description: Hello, I am trying to upgrade gettext on a 10.7.5 Lion with Macports 2.2.0. I read the tickets #34221 and #36740 but I think this is a different problem. The upgrade got stuck during the configure stage and using -v -d I can see that the last item is the check for ranlib. This is the output of configure, please tell me if anyone requires more information. {{{ 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 gcc... /usr/bin/clang checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/clang accepts -g... yes checking for /usr/bin/clang option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/clang... none checking for bison... bison -y checking whether to use Java... yes checking how to run the C preprocessor... /usr/bin/clang -E checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for Java compiler... javac -target 1.1 -source 1.3 checking for jar... jar checking for preferred C# implementation... no checking for C# compiler... no checking build system type... x86_64-apple-darwin11.4.2 checking host system type... x86_64-apple-darwin11.4.2 checking for Minix Amsterdam compiler... no checking for ar... ar checking for ranlib... ranlib }}} I would greatly appreciate help. -- Comment: Please attach the complete main.log after cleaning the port. In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers gettext}}}). -- Ticket URL: <https://trac.macports.org/ticket/40463#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#40463: gettext hangs during upgrade ------------------------------+-------------------------- Reporter: saschaschnepp@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: gettext | ------------------------------+-------------------------- Comment (by larryv@…): Replying to [ticket:40463 saschaschnepp@…]:

The upgrade got stuck during the configure stage and using -v -d I can see that the last item is the check for ranlib.

What does “stuck” mean? How long did you wait? -- Ticket URL: <https://trac.macports.org/ticket/40463#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#40463: gettext hangs during upgrade ------------------------------+-------------------------- Reporter: saschaschnepp@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: gettext | ------------------------------+-------------------------- Comment (by ryandesign@…): Replying to [ticket:40463 saschaschnepp@…]:

I read the tickets #34221 and #36740 but I think this is a different problem.

Right: #36740 is a duplicate of #34221, which should only have affected Mountain Lion and was fixed in MacPorts 2.2.0.

The upgrade got stuck during the configure stage and using -v -d I can see that the last item is the check for ranlib. This is the output of configure, please tell me if anyone requires more information.

I'm having trouble reconciling your output with what I get when I configure gettext. Since the main.log is getting truncated, let's try again, directing stdout and stderr to a file. I also see your previous attempt was building universal; let's try non-universal for simplicity. Please try: {{{ sudo port clean gettext sudo port -d configure gettext -universal 2>&1 | tee new.log }}} Then when it hangs, interrupt by pressing `^C` and attach the new.log file to this ticket. I'll compare that with mine. -- Ticket URL: <https://trac.macports.org/ticket/40463#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#40463: gettext hangs during upgrade ------------------------------+-------------------------- Reporter: saschaschnepp@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: gettext | ------------------------------+-------------------------- Comment (by ryandesign@…): Ok, well the next line in my configure output is: {{{ checking whether /usr/bin/clang and cc understand -c and -o together... yes }}} so that test must be failing. We should look into the configure script, see what they're doing, then you try to do the same thing on the command line. Perhaps we could start by determining the version of your `clang` and `cc`: could you run: {{{ /usr/bin/clang -v cc -v }}} -- Ticket URL: <https://trac.macports.org/ticket/40463#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#40463: gettext hangs during upgrade ------------------------------+-------------------------- Reporter: saschaschnepp@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: gettext | ------------------------------+-------------------------- Comment (by ryandesign@…): Replying to [comment:8 saschaschnepp@…]:

On my system this produces: {{{ sascha$ /usr/bin/clang -v Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.4.2 Thread model: posix }}}

That's old; the current version is 4.2 not 3.1. Please update to Xcode 4.6.3, then open Xcode, go to its Preferences window, to the Downloads section, and update the command line tools.

and {{{ sascha$ cc -v Using built-in specs. COLLECT_GCC=/opt/local/bin/gcc-mp-4.7 COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin11/4.7.3 /lto-wrapper Target: x86_64-apple-darwin11 Configured with: ../gcc-4.7.3/configure --prefix=/opt/local --build=x86_64-apple-darwin11 --enable- languages=c,c++,objc,obj-c++,lto,fortran,java --libdir=/opt/local/lib/gcc47 --includedir=/opt/local/include/gcc47 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-4.7 --with-libiconv-prefix=/opt/local --with-local-prefix=/opt/local --with-system-zlib --disable-nls --program- suffix=-mp-4.7 --with-gxx-include-dir=/opt/local/include/gcc47/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with- ppl=/opt/local --with-cloog=/opt/local --enable-cloog-backend=isl --disable-cloog-version-check --enable-stage1-checking --disable-multilib --enable-lto --enable-libstdcxx-time --with-as=/opt/local/bin/as --with- ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with- bugurl=https://trac.macports.org/newticket --disable-ppl-version-check --with-pkgversion='MacPorts gcc47 4.7.3_1' Thread model: posix gcc version 4.7.3 (MacPorts gcc47 4.7.3_1) }}}

I presume you've deliberately changed `cc` to be this? Perhaps using `port select gcc`? If so, try setting it back the way it was before building gettext. -- Ticket URL: <https://trac.macports.org/ticket/40463#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X

#40463: gettext hangs during upgrade ------------------------------+-------------------------- Reporter: saschaschnepp@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: gettext | ------------------------------+-------------------------- Changes (by macsforever2000@…): * cc: bstfr.forver_77@… (added) Comment: Cc reporter of duplicate #41277. -- Ticket URL: <https://trac.macports.org/ticket/40463#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X