382107 – Why is =sys-devel/gcc-4.6.1-r1 still hard-masked?

Bug 382107 - Why is =sys-devel/gcc-4.6.1-r1 still hard-masked?

Summary: Why is =sys-devel/gcc-4.6.1-r1 still hard-masked?

Status:	RESOLVED DUPLICATE of bug 346809

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	AMD64 Linux

Importance:	Lowest QA (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-09-07 02:46 UTC by Ch_E
Modified:	2011-09-07 03:57 UTC (History)
CC List:	1 user (show)

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

Attachments
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 Ch_E 2011-09-07 02:46:23 UTC

I use the =sys-devel/gcc-4.6.1 (and later gcc-4.6.1-r1) compiler version which is still hard-masked for testing.

Almost the whole system compiles fine when using =sys-devel/gcc-4.6.1-r1. The only ebuild the fails to compile is ruby, which is not used/installed any more on my machine since I don't need any ebuild that has ruby as a dependency. Aren't there already patches upstream that fixes the GCC-4.6.1 problem in ruby?

So why is =sys-devel/gcc-4.6* still hard-masked? Are there any other ebuild that fail to compile when using the GCC 4.6 series?

Comment 1 Mike Gilbert gentoo-dev

2011-09-07 03:57:11 UTC

See bug 346809 for packages broken by gcc-4.6.

*** This bug has been marked as a duplicate of bug 346809 ***