Opened 11 years ago
Closed 11 years ago
#40466 closed defect (fixed)
libgcc-devel @4.9-20130908 fails to build due to internal compiler error
| Reported by: | feliks.kluzniak@… | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | libgcc-devel |
Description (last modified by larryv (Lawrence Velázquez))
Attempting to build the new version of libgcc-devel to check whether the problem described in ticket #40284 still persists. Seems to be building OK, using reasonable amounts of memory, but after about an hour the build failed:
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc-devel/work/gcc-4.9-20130908/gcc/cp/pt.c: In function 'tree_node* maybe_get_template_decl_from_type_decl(tree)': :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc49/libgcc-devel/work/gcc-4.9-20130908/gcc/cp/pt.c:7064:1: internal compiler error: in propagate_threaded_block_debug_into, at tree-ssa-threadedge.c:623 :info:build maybe_get_template_decl_from_type_decl (tree decl) :info:build ^
I attach the log.
Attachments (1)
Change History (6)
Changed 11 years ago by feliks.kluzniak@…
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
| Description: | modified (diff) |
|---|---|
| Owner: | changed from macports-tickets@… to mww@… |
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
Please test again with 4.9-20130915 which builds fine for me.
comment:4 Changed 11 years ago by feliks.kluzniak@…
I donfirm that the latest version installs from binaries without problems.
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
This isn’t really our problem. Have you reported it upstream?