gettext @0.18.3.1_1 build failure

[c.sarfuguet@…]

I have a build problem when trying to install the gettext port.

The errors are:

:info:build ./stdio.h:901:27: error: expected identifier
:info:build                           (const void *__restrict, size_t, size_t,
:info:build                           ^
:info:build ./stdio.h:905:27: error: expected identifier
:info:build                           (const void *__restrict, size_t, size_t,

I look a little bit more on the problem and i found that the concerned files are in:

gettext-runtime/gnulib-lib/stdio.in.h >> stdio.h
gettext-tools/gnulib-lib/stdio.in.h >> stdio.h
gettext-tools/libgettextpo/stdio.in.h >> stdio.h

I'm working on Mac OSX 10.9 (Mavericks)

xcodebuild -version

Xcode 5.0.1
Build version 5A2053

xcode-select --version

xcode-select version 2333

The macport build log is attached to this ticket.

Hereafter the terminal output:

terminal output

--->  Computing dependencies for gettext
--->  Fetching distfiles for gettext
--->  Verifying checksums for gettext
--->  Extracting gettext
--->  Configuring gettext
--->  Building gettext
Error: org.macports.build for port gettext returned: command execution failed
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 get text failed

[c.sarfuguet@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

The log you attached is not from a clean attempt; ​clean and try again.

The log shows you are on Mavericks. Did you follow the migration instructions? gettext builds fine for me and others.

[c.sarfuguet@…]

port install gettext log file

[c.sarfuguet@…]

Replying to ryandesign@…:

The log you attached is not from a clean attempt; ​clean and try again.

The log shows you are on Mavericks. Did you follow the migration instructions? gettext builds fine for me and others.

Thank you Ryan for your answer.

I did a complete reinstall of Xcode 5.0.1 and Macports 2.2.1 but i'm still having the same problem
building the gettext port. I attached the log file of the new clean attempt.

[c.sarfuguet@…]

I forgot to tell that i've followed the migration instruction and there was a problem
when executing the xcode-select --install command. After executing this command
i got the following message:

Can't install the software because it is not currently available from the Software Update server.

But apparently the Xcode 5.0.1 came with the command line tools integrated so i though it was
not a real problem.

[ryandesign (Ryan Carsten Schmidt)]

Xcode does not come with command line tools. They must be installed separately as it says in our documentation.

Please confirm whether you have actually installed the command line tools. One way to find out is to see if you have the file /usr/lib/tclConfig.sh. If not, you have not installed the command line tools.

[c.sarfuguet@…]

Replying to ryandesign@…:

Xcode does not come with command line tools. They must be installed separately as it says in our documentation.

Please confirm whether you have actually installed the command line tools. One way to find out is to see if you have the file /usr/lib/tclConfig.sh. If not, you have not installed the command line tools.

I have the file /usr/lib/tclConfig.sh

[ryandesign (Ryan Carsten Schmidt)]

Ok, I've compared your log to mine. Many differences I don't understand. Could you attach your config.log files? gettext runs multiple configure scripts so there are multiple config.log files; this command shows you where they are:

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

If you could rename them so I know which is which and attach them to this ticket I can compare them with mine and hopefully find out why your build is failing.

[c.sarfuguet@…]

config.log files in gettext work directory

[c.sarfuguet@…]

I added the config.log files.

Thanks again for the help

Replying to ryandesign@…:

Ok, I've compared your log to mine. Many differences I don't understand. Could you attach your config.log files? gettext runs multiple configure scripts so there are multiple config.log files; this command shows you where they are:

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

If you could rename them so I know which is which and attach them to this ticket I can compare them with mine and hopefully find out why your build is failing.

[ryandesign (Ryan Carsten Schmidt)]

I haven't finished comparing the files, but let's start with one difference I see. Your main.log says:

:info:configure checking whether we are using the GNU C Library 2 or newer... yes

:info:configure checking for features.h... yes

while mine says:

:info:configure checking whether we are using the GNU C Library 2 or newer... no

:info:configure checking for features.h... no

The former result appears to be due to the latter. The question is: where is features.h on your system and how did it get there? It's not on my system, which makes me wonder if it should be there on yours.

[c.sarfuguet@…]

I looked for the file features.h and i found it in /usr/include. I begun having
these problems with gettext port after having upgraded from Mountain Lion
to Mavericks. Is it possible that some files from these system directories
were kept after the upgrade?

Replying to ryandesign@…:

I haven't finished comparing the files, but let's start with one difference I see. Your main.log says:

:info:configure checking whether we are using the GNU C Library 2 or newer... yes

:info:configure checking for features.h... yes

while mine says:

:info:configure checking whether we are using the GNU C Library 2 or newer... no

:info:configure checking for features.h... no

The former result appears to be due to the latter. The question is: where is features.h on your system and how did it get there? It's not on my system, which makes me wonder if it should be there on yours.

[ryandesign (Ryan Carsten Schmidt)]

I doubt it. That is, I doubt features.h belongs on any version of OS X. Could you attach your features.h here so I can take a look?

[c.sarfuguet@…]

features.h

[c.sarfuguet@…]

I attached the file.

When i was using Mountain Lion, i've installed gcc44 (macports version). I don't know
it this could install some glib files in the /usr/ path. I find it strange because my port
installation path is and was /opt/local.

Replying to ryandesign@…:

I doubt it. That is, I doubt features.h belongs on any version of OS X. Could you attach your features.h here so I can take a look?

[ryandesign (Ryan Carsten Schmidt)]

No, installing a MacPorts port would not cause this.

You didn't by chance copy this and other files there by following some guide, like ​this one?

I'd remove the file (move it to the desktop if you want to keep it around for awhile), then clean gettext and try again.

When was the file last modified? Are there any other files in /usr/include modified at the same time, that might also not belong?

[c.sarfuguet@…]

I think you are right. Actually, some months ago i was working in an elf loader
and i remember installing severals files to decode the ELF format in the /usr/include directory
. Bad idea...

I will try to remove them and reinstall gettext

Replying to ryandesign@…:

No, installing a MacPorts port would not cause this.

You didn't by chance copy this and other files there by following some guide, like ​this one?

I'd remove the file (move it to the desktop if you want to keep it around for awhile), then clean gettext and try again.

When was the file last modified? Are there any other files in /usr/include modified at the same time, that might also not belong?

[ryandesign (Ryan Carsten Schmidt)]

Right, bad idea. OS X does not use GNU lib C or ELF files, so installing header files that make configure scripts think it does will only lead to sadness. /usr/include is belongs to the OS vendor; it's not meant for end users to modify.

[c.sarfuguet@…]

That works.

"/usr/include is belongs to the OS vendor" -> I will remember that.

Thanks a lot for the help.

Replying to c.sarfuguet@…:

I think you are right. Actually, some months ago i was working in an elf loader
and i remember installing severals files to decode the ELF format in the /usr/include directory
. Bad idea...

I will try to remove them and reinstall gettext

Replying to ryandesign@…:

No, installing a MacPorts port would not cause this.

You didn't by chance copy this and other files there by following some guide, like ​this one?

I'd remove the file (move it to the desktop if you want to keep it around for awhile), then clean gettext and try again.

When was the file last modified? Are there any other files in /usr/include modified at the same time, that might also not belong?