| Summary: | gcc-config and gcc: File collisons in /usr/bin/g77 and /usr/bin/i686-pc-linux-gnu-g77 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jakub, truedfx, waebbl |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Alexander Skwar
2004-11-29 15:34:01 UTC
*** Bug 72745 has been marked as a duplicate of this bug. *** err, meant to mark the dupe the other direction, but oh well fixed in gcc-config-1.3.7-r3 *** Bug 73568 has been marked as a duplicate of this bug. *** I want to add a comment to the comment Bug #73568 which has been marked as a duplicate of this bug. Wouldn't it be a solution (at least temporary) to bring the gcc-config-1.3.6-r3.ebuild file back into portage, as long as gcc-config-1.3.7 isn't marked stable? I asked this already in Bug #72745. See comment #3. The problem is not only that gcc-config could not update, but also, that the whole system is inable to do any(!!!) updates. Every day I need to copy my backed-up version of the gcc-config-1.3.6-r3.ebuild back into the portage tree to be able to do any updates. The missing ebuild of the already installed version of gcc-config causes portage to break the update. |