Summary: | [cross-mingw32/gcc] gcc fails at gcc-stage2 due to GCC_NO_EXECUTABLES | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | cretin, tek666, togge.gentoo |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
MinGW32 info log
MinGW32 gcc-stage2 log |
Description
Dennis Schridde
2006-09-22 05:57:53 UTC
Created attachment 97743 [details]
MinGW32 info log
Created attachment 97744 [details]
MinGW32 gcc-stage2 log
*** Bug 149365 has been marked as a duplicate of this bug. *** I've experienced something close to this problem when upgrading GCC in an existing cross-mingw32, to get around it I just started from scratch: emerge --unmerge cross-mingw32/gcc cross-mingw32/mingw-runtime cross-mingw32/w32api cross-mingw32/binutils Remove cross-mingw32 stuff from /etc/portage/package.keywords, package.use, categories rm -Rf /usr/local/portage/cross-mingw32 Then just rerun "crossdev mingw32" and it works. Unfortunately, I have no idea why though - possibly library breakage between versions. that's a whole lot of effort ... why didnt you just run `crossdev -C mingw32` ? would need the config.log to actually trace this down |