libgcc build fail on Yosemite

[ja_macports@…]

After an update to Yosemite, Xcode 6.1 and MacPorts 2.3.2. I'm rebuilding everything and I have a strange error preventing me to build libgcc

[larryv (Lawrence Velázquez)]

Uh, okay? So what’s the error?

[ja_macports@…]

main.log from libgcc build

[ja_macports@…]

Forgot to mention, that despite the message 'The Xcode Command Line Tools don't appear to be installed; most ports will likely fail to build' Command line tools 6.1 are installed as:

xcode-select -p /Applications/Xcode.app/Contents/Developer

[larryv (Lawrence Velázquez)]

You don’t have the Command Line Tools installed, you have Xcode installed. Many of the executables in /usr/bin are shims that call the executables in Xcode automatically, but many ports still try to find headers in /usr/include.

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

The Command Line Tools install those headers; install them with xcode-select --install, clean libgcc, and try again.

[ja_macports@…]

It doesn't seem to find the <stdio.h> headers while building stage1-bubble I'm trying to reinstall Xcode command line just to be certain. (But I have already rebuilt a lot of ports)

Ok that was it, I had 6 updates for the command line tools in Software Update. Now Software Updates tells me I have installed the command line tools 18 times! (Don't tell me I didn't :) ) Looks like a glitch in Apple tools.

Thanks

[larryv (Lawrence Velázquez)]

Did that work? Make sure /usr/include exists.

[ja_macports@…]

Yes /usr/include looks complete now. Install succesful. Though this morning Software Update had to install two more time the Command Line tools! That makes 20.

[larryv (Lawrence Velázquez)]

Well that sure sounds weird, but we’ll call it fixed.