Gettext fails

[rplatjes@…]

Did a clean install of macports on my Yosemite upgrade install (removed MacPorts before upgrading the OS as per instructions).

While trying to reinstall packages I have a lot of problems. One is that I can't seem to get Numpy installed. It keeps hanging on gettext, so I tried to get that installed separate.

[rplatjes@…]

main.log

[neverpanic (Clemens Lang)]

Please Cc the maintainer (if any) when reporting bugs against ports.

Problem is an attempted redefinition of ptrdiff_t by /usr/include/sys/_types/_ptrdiff_t.h, but ptrdiff_t is #defined to be long, so essentially the header tries to redefine long. Gettext's configure script would avoid doing that if it found a usable ptrdiff_t provided by system headers. However, on your system, this happens instead:

377	:info:configure checking stddef.h presence... yes
378	:info:configure configure: WARNING: stddef.h: present but cannot be compiled
379	:info:configure configure: WARNING: stddef.h:     check for missing prerequisite headers?
380	:info:configure configure: WARNING: stddef.h: see the Autoconf documentation
381	:info:configure configure: WARNING: stddef.h:     section "Present But Cannot Be Compiled"
382	:info:configure configure: WARNING: stddef.h: proceeding with the compiler's result
383	:info:configure configure: WARNING:     ## -------------------------------------- ##
384	:info:configure configure: WARNING:     ## Report this to bug-gnu-gettext@gnu.org ##
385	:info:configure configure: WARNING:     ## -------------------------------------- ##

Please attach /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.3/config.log so we can see the error message for this compiler invocation.

[ryandesign (Ryan Carsten Schmidt)]

After upgrading to Yosemite, did you remember to upgrade to Xcode 6.1 and install Xcode 6.1's command line tools?

[rplatjes@…]

Replying to ryandesign@…:

After upgrading to Yosemite, did you remember to upgrade to Xcode 6.1 and install Xcode 6.1's command line tools?

Yes. So far as I know (I'm really not that deep into development, just enough to do some damage). I downloaded xCode 6.1. from within Xcode installed command line tools.

As for the asked config.log

Did

sudo cp /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gettext/gettext/work/gettext-0.19.3/config.log /Users/xxxx/Desktop 

It returns a 'No such file'. I think there went something really wrong when I did a OS upgrade. Other MacPorts packages won't install either. I think the quickest solution for me now is to try a OS reinstall (repair). I need a working Python27 via MacPorts tomorrow. So don't have much time to do real deep troubleshooting.

I think it's best to close this ticket for now. I'm sorry for the inconvenience.

[ryandesign (Ryan Carsten Schmidt)]

I doubt you need to do anything drastic. Let's just see what the config.logs say. Gettext is unique in that it has several of them. Please attach all of them. You can locate them with this command:

find $(port work gettext) -name config.log

[ryandesign (Ryan Carsten Schmidt)]

I've compared our main.log files, and the first major difference is that mine says:

:info:configure checking for ANSI C header files... yes

while yours says:

:info:configure checking for ANSI C header files... no

These header files are part of what's installed with the command line tools. So you might try reinstalling the command line tools, using the installer package you can download from the Apple developer web site.

[rplatjes@…]

Replying to ryandesign@…:

I've compared our main.log files, and the first major difference is that mine says:

:info:configure checking for ANSI C header files... yes

while yours says:

:info:configure checking for ANSI C header files... no

These header files are part of what's installed with the command line tools. So you might try reinstalling the command line tools, using the installer package you can download from the Apple developer web site.

Really nice of you for thinking along. And I'm sorry I saw you last answer a little to late to take your advice that maybe it could be dealt with a little less drastic.

I suspected something went wrong with Xcode. So I did a new repair install on the OS (I like drastic 'fresh starts' when something is going wrong which I don't fully understand)

Before the repair install I removed Macports (as per instruction found here ​https://guide.macports.org/chunked/installing.macports.uninstalling.html) . I removed Xcode.

I'm just in the process of reinstalling Xcode. II downloaded the standalone install .dmg for the command line tools.

Hopefully I get things running as I need now.

[rplatjes@…]

Oke. Just saw gettext being installed without a problem.

So fault was on my end. I Now I think of it it could be that I had an Xcode 6.1 version which I had to download from the Apple dev website because it wasn't available yet from the Appstore. Maybe there was some version problems there with command line tools?

Anyway Nothing to see here, case closed.

[ryandesign (Ryan Carsten Schmidt)]

Ok, I'm glad you got it working.