libgcc build failure on Mavericks

[ilg@…]

I'm trying to build gcc48 on an empty MacPorts (absolutely the first install).

I used:

  sudo port install gcc48 +universal

The result is

--->  Building libgcc
Error: org.macports.build for port libgcc returned: command execution failed
Error: Failed to install libgcc
Please see the log file for port libgcc for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/main.log
Error: The following dependencies were not installed: libgcc
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port gcc48 failed

I first tried to upgrade the old 4.8.1 I had, but it also failed. I then removed everything and tried from scratch, to avoid interferences, but it also failed.

I would appreciate a solution, since currently I have no 4.8 available at all.

[ilg@…]

the build log, archived

[mf2k (Frank Schima)]

In the future, please use WikiFormatting, fill in the Port field with the port that actually fails to build and Cc the port maintainers (port info --maintainers libgcc).

[jeremyhu (Jeremy Huddleston Sequoia)]

:info:build make[2]: *** [all-stage1-gcc] Error 2

But I don't see the actual error.

FWIW, gcc48 is installed here just fine:

~ $ gcc-mp-4.8 --version
gcc-mp-4.8 (MacPorts gcc48 4.8.2_0+universal) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[ilg@…]

Replying to jeremyhu@…:

But I don't see the actual error.

the build output is in the original post, and the log is in the attached file.

FWIW, gcc48 is installed here just fine:

there are probably some dependencies that in your configuration were satisfied.

please retry on a completely empty MacPorts repository, as the first installed port.

to fully reproduce my case, install gcc48 +universal, but I think you will obtain the same result if you try directly with libgcc

[jeremyhu (Jeremy Huddleston Sequoia)]

Replying to ilg@…:

Replying to jeremyhu@…:

But I don't see the actual error.

the build output is in the original post, and the log is in the attached file.

Yes, I am aware. That is where I sourced the information that I pasted into my comment. That message from make is the first indication I see of an error. Thus I don't see anything logging the actual error, just make complaining that an error occurred and then base aborting because of make erring out.

FWIW, gcc48 is installed here just fine:

there are probably some dependencies that in your configuration were satisfied.

please retry on a completely empty MacPorts repository, as the first installed port.

to fully reproduce my case, install gcc48 +universal, but I think you will obtain the same result if you try directly with libgcc

It built fine on the build bots as well.

[ilg@…]

Replying to jeremyhu@…:

... That message from make is the first indication I see of an error.

that's correct, everything up to that point is looking good

Thus I don't see anything logging the actual error, just make complaining that an error occurred and then base aborting because of make erring out.

I did a search for 'error' from the end up in the attached log, and I discovered the following:

:info:build xgcc: error trying to exec 'cc1': execvp: No such file or directory
...
:info:build The directory that should contain system headers does not exist:
:info:build   /usr/include
:info:build make[3]: *** [stmp-fixinc] Error 1

I don't know the reason for the first execvp, but /usr/include does not exist on 10.9.1

does this help?

if not, can you be more specific on what info you would like to have to reproduce and identify the problem?

It built fine on the build bots as well.

do these bots run on a standard 10.9.1 and try to install the package on an empty repo?

do you have a sequence of commands to try on my system, to get some more info?

[neverpanic (Clemens Lang)]

/usr/include exists if you install the command line tools using xcode-select --install. Does /Library/Developer/CommandLineTools/usr/bin/make exist on your system? If not, you need to install the command line tools.

[ilg@…]

Replying to cal@…:

/usr/include exists if you install the command line tools using xcode-select --install. Does /Library/Developer/CommandLineTools/usr/bin/make exist on your system? If not, you need to install the command line tools.

That was an Apple strange thing. I have latest Xcode 5.0.2, and I also had (apparently only some of) the command line tools, installed from within Xcode -> Preferences -> Downloads, and they looked functional (latest Apple clang, git and all usual tools were available). but the include headers were not there. I guess the upgrade from the previous Xcode did not went well and the command tools were partly missing.

I just manually reinstalled

 command_line_tools_os_x_mavericks_for_xcode__late_october_2013.dmg

from the developer site (I guess similar to xcode-select --install, but I wanted to be sure what I'm doing) and the headers showed up. :-)

Building libgcc passed, and so gcc48.

I believe we can close this ticked, sorry for any inconveniences.

Thank you,

Liviu

[neverpanic (Clemens Lang)]

MacPorts 2.3 will contain a check warning you if that happens again.

Xcode 5 on Mavericks no longer has a way to install the command line tools from the Xcode Preferences; what you had installed must have been from an older Xcode install.

[ilg@…]

Replying to cal@…:

MacPorts 2.3 will contain a check warning you if that happens again.

that's a great idea. probably the test should be performed before each 'port install', to account for all new Xcode updates. Xcode is quite a fast moving target...