Summary: | [build/gcc] gcc-4.1.1-r3 ICES while building on alpha/ev6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | dawe <daweonline> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | alpha |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | Alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
bzip2 preprocessed source
the emerge log |
Description
dawe
2007-05-14 09:49:29 UTC
Created attachment 119200 [details]
bzip2 preprocessed source
Created attachment 119204 [details]
the emerge log
does it fail in the same place every time with the same error message ? (In reply to comment #3) > does it fail in the same place every time with the same error message ? > Yes. I've tried to manually compile gcc with portage configuration layout (i.e. passing to configure the same args portage does) and it works as I add -Wa,-mev6 CFLAG. I've noticed that this flag is not included in ALLOWED_FLAGS while emerging gcc. I've done a working gcc 4.1.1 and then used it to emerge gcc-4.1.1, it works. What is strange is that the -Wa,-mev6 flag is not needed by gcc 4.1.1 to compile gcc 4.1.1 (in fact portage still excludes it from ALLOWED_FLAGS) just built gcc-4.1.2 on an alphaev68 with -mcpu=ev67 and CHOST=alphaev68 -Wa belongs in ASFLAGS, not CFLAGS that said, there is no reason at all you should be setting that yourself |