Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 611172 - [ICE/4.9] dev-libs/libyaml fails to emerge under i686-w64-mingw32: internal compiler error: in symtab_nonoverwritable_alias, at symtab.c:1252
Summary: [ICE/4.9] dev-libs/libyaml fails to emerge under i686-w64-mingw32: internal c...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-28 07:28 UTC by hanetzer
Modified: 2017-03-01 22:36 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (emerge.info,3.49 KB, text/plain)
2017-02-28 07:28 UTC, hanetzer 		Details
emerge -pqv (emerge.pqv,107 bytes, text/plain)
2017-02-28 07:28 UTC, hanetzer 		Details
environment (environment,91.97 KB, text/plain)
2017-02-28 07:29 UTC, hanetzer 		Details
build.log (build.log,11.25 KB, text/x-log)
2017-02-28 07:30 UTC, hanetzer 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hanetzer 2017-02-28 07:28:19 UTC 
Created attachment 465464 [details]
emerge --info

Attempting to get a mingw-w64 ruby build environment setup, failure on this dep.
Comment 1 hanetzer 2017-02-28 07:28:51 UTC 
Created attachment 465466 [details]
emerge -pqv
Comment 2 hanetzer 2017-02-28 07:29:51 UTC 
Created attachment 465468 [details]
environment
Comment 3 hanetzer 2017-02-28 07:30:19 UTC 
Created attachment 465470 [details]
build.log
Comment 4 hanetzer 2017-02-28 10:02:22 UTC 
https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-libyaml
Applying the patches here allow for build.
Comment 5 SpanKY gentoo-dev 2017-03-01 22:36:20 UTC 
you're using old versions of binutils & toolchain.  your emerge info says you're using binutils 2.24 and gcc 4.9.2, neither of which we support anymore.

upgrade to recent versions and see if the issue is still there.