gcc49: fatal error: stdio.h: No such file or directory

[dcnicholls]

Yosemite 10.10.1, Xcode 6.1 (with command line tools installed as part of it)

The error:

--->  Building gcc49
Error: org.macports.build for port gcc49 returned: command execution failed
Please see the log file for port gcc49 for details:

The log file is attached

The first error in the log relating to this appears to be:

:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/gcc49/work/gcc-4.9.2/libgcc/../gcc/tsystem.h:87:19: fatal error: stdio.h: No such file or directory

I was able to install gcc48 with no trouble. This is a completely clean install. All references to the previous (Mavericks) install of Macports were removed. Following the error message instructions, I did a "sudo port clean gcc49" and re-ran the install. Same result.

[dcnicholls]

Main.log referred to in error message. It shows the error twice, as I tried to install twice.

[ryandesign (Ryan Carsten Schmidt)]

The error "stdio.h: No such file or directory" usually means you have not installed the Xcode command line tools. If you haven't done so, please do, then clean gcc49 again. gcc49 builds fine for me on Yosemite.

[dcnicholls]

I did have the command line tools installed, as indicated by the command "xcode-select -p". However, I seem to have fixed it: I reinstalled XCode 6.1. (using the route offered by "xcode-select --install") The first thing I noticed was that when I now enter "xcode-select --install" again it now tells me the tools are already installed. Before, while the tools were there, they didn't register as present with the "xcode-select --install" command.

Following the XCode re-install, the gcc49 port compile did not crash, though it took 25 minutes to compile on this SSD 2.8GHz machine, whereas gcc48 compiled in about 3 minutes.

Something is still a bit odd (why the compile time difference?), but it appears to be working.

[larryv (Lawrence Velázquez)]

Replying to dcn@…:

I did have the command line tools installed, as indicated by the command "xcode-select -p".

The output of xcode-select --print-path should indicate Xcode, not the Command Line Tools. If this is not the case, please switch the developer directory to Xcode.

Following the XCode re-install, the gcc49 port compile did not crash, though it took 25 minutes to compile on this SSD 2.8GHz machine, whereas gcc48 compiled in about 3 minutes.

Something is still a bit odd (why the compile time difference?), but it appears to be working.

You are getting a binary archive for gcc48 but are compiling gcc49 from source.