Opened 10 years ago

Closed 10 years ago

#40678 closed defect (worksforme)

gcc48 / libgcc not building on Mavericks

Reported by: AP1010 Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc: jeremyhu (Jeremy Huddleston Sequoia), bonoba@…, 1002536r@…
Port: gcc48

Description

When I try to build gcc48 the build fail at the stage of libgcc. It looks like xgcc is not finding stdio.h for some reason. I do realize that Mavericks is still unreleased, but I am working with GM seed, and Xcode 5.0.1 GM, so there is a very good chance this problem will be present in the released version.

Attachments (2)

main.log (3.9 MB) - added by AP1010 10 years ago.
main.2.log (3.9 MB) - added by 1002536r@… 10 years ago.
Different issue but related to the same port.

Change History (15)

Changed 10 years ago by AP1010

Attachment: main.log added

comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: jeremyhu@… added; mww@… removed
Owner: changed from macports-tickets@… to mww@…
Port: gcc48 added

comment:2 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: invalid
Status: newclosed

User error:

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

You have not properly installed all dependencies of MacPorts.

comment:3 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

And yes, it works for me.

comment:4 Changed 10 years ago by AP1010

  1. does it work for you on Mavericks? (it worked for me on Mountain Lion)
  2. Any suggestions what are the dependencies I failed to install? - I built new MacPorts from source and built quite few ports from source. Mostly things work.

The funny part is: stdio.h does exist. clang has no problem finding it. It is the second stage (xgcc that does not find it)

Last edited 10 years ago by AP1010 (previous) (diff)

comment:5 in reply to:  4 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Replying to arthur@…:

  1. does it work for you on Mavericks? (it worked for me on Mountain Lion)

As I said, yes. Also, you are not allowed to discuss Mavericks in public. Please followup by emial.

  1. Any suggestions what are the dependencies I failed to install? - I built new MacPorts from source and built quite few ports from source. Mostly things work.

The funny part is: stdio.h does exist. clang has no problem finding it. It is the second stage (xgcc that does not find it)

You have /usr/include/stdio.h installed by the Xcode command line tools?

comment:6 Changed 10 years ago by bonoba@…

Cc: bonoba@… added

Cc Me!

comment:7 Changed 10 years ago by 1002536r@…

Cc: 1002536r@… added

Cc Me!

comment:8 Changed 10 years ago by 1002536r@…

Cc: 1002536r@… removed

Cc Me!

comment:9 Changed 10 years ago by 1002536r@…

Cc: 1002536r@… added

Cc Me!

Changed 10 years ago by 1002536r@…

Attachment: main.2.log added

Different issue but related to the same port.

comment:10 Changed 10 years ago by 1002536r@…

Resolution: invalid
Status: closedreopened

There does seem to be an issue on the public release of Mavericks with libgcc (as shown in my main.log (called main.2.log)). I wasn't sure if this was worthy of a new ticket so I reopened this, I hope that this is acceptable.

comment:11 in reply to:  10 ; Changed 10 years ago by AP1010

Replying to 1002536r@…:

There does seem to be an issue on the public release of Mavericks with libgcc (as shown in my main.log (called main.2.log)). I wasn't sure if this was worthy of a new ticket so I reopened this, I hope that this is acceptable.

A part of your log says: The directory that should contain system headers does not exist: :info:build /usr/include

Looks like your command line tools are not installed.

comment:12 in reply to:  11 Changed 10 years ago by 1002536r@…

Replying to arthur@…:

Replying to 1002536r@…:

There does seem to be an issue on the public release of Mavericks with libgcc (as shown in my main.log (called main.2.log)). I wasn't sure if this was worthy of a new ticket so I reopened this, I hope that this is acceptable.

A part of your log says: The directory that should contain system headers does not exist: :info:build /usr/include

Looks like your command line tools are not installed.

Weird, "xcode-select --install" saw an update for the tools this time, it didn't last night. libgcc 4.8.1_3 successfully activated.

Thank you for your time and apologies for any confusion caused.

Gordon

comment:13 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: worksforme
Status: reopenedclosed
Note: See TracTickets for help on using tickets.