Summary: | Build fails trying to run ppc64 binaries on powerpc-apple-darwin8.5.0 | ||
---|---|---|---|
Product: | gcc | Reporter: | Malcolm Purvis <malcolmpurvis> |
Component: | bootstrap | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gcc-bugs |
Priority: | P3 | ||
Version: | 4.1.0 | ||
Target Milestone: | --- | ||
Host: | powerpc-apple-darwin8.5.0 | Target: | powerpc-apple-darwin8.5.0 |
Build: | powerpc-apple-darwin8.5.0 | Known to work: | |
Known to fail: | Last reconfirmed: |
Description
Malcolm Purvis
2006-03-10 02:49:02 UTC
Use --disable-multilib. (In reply to comment #1) > Use --disable-multilib. > This has fixed the problem. Thank you. However, I would query the determination that this is not a bug. I don't expect the default configuration of a common system in an official release to fail. Either multilib should be disabled by default for this target or special mention of be made in INSTALL/specific.html (as I have subsequently discovered the case for mips-sgi-irix6 and sparc-sun-solaris2*). Just wasted a day or so on this as well. Sure seems like a bug to me. Why should it auto-detect which CPU it is building upon and then attempt to build a compiler that is guaranteed to break? Does it attempt to execute code for other cross compiler targets? |