Opened 11 years ago
Closed 9 years ago
#40604 closed defect (wontfix)
qt4-mac: internal compiler error: in lower_stmt, at gimple-low.c:286
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.0 |
Keywords: | leopard | Cc: | |
Port: | qt4-mac |
Description
Building qt4-mac fails with gcc-4.2 on Leopard PowerPC with:
html/HTMLTitleElement.cpp: In member function ?void WebCore::HTMLTitleElement::setText(const WTF::String&)?: html/HTMLTitleElement.cpp:107: internal compiler error: in lower_stmt, at gimple-low.c:286 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://developer.apple.com/bugreporter> for instructions.
Of course submitting a bug report about gcc to Apple is pointless by now.
This probably came about due to MacPorts 2.2 which now uses gcc-4.2 as the default compiler on Leopard instead of gcc-4.0.
I found what seems to be an upstream bug report about this problem for FSF GCC 4.2.3, fixed in 4.3/4.4, but of course that doesn't help us with Apple GCC. However I haven't had problems building qt4-mac on Snow Leopard, which uses a later build of Apple gcc-4.2, so I assume Apple either backported or reinvented the fix for this by Snow Leopard, but of course that doesn't help Leopard users.
#40422 requests gcc-4.0 be blacklisted. Based on my experience here, we may also have to blacklist Leopard's gcc-4.2 (which is build 5577 or earlier). Xcode 3.2.6 has gcc-4.2 build 5666 dot 3 so we don't need to blacklist that, but I don't know where between 5578 and 5666.3 the problem was fixed.
I have not tested Leopard Intel yet. It's also possible it's a PowerPC-only problem.
Attachments (1)
Change History (5)
Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | qt4-mac.leopard.ppc.main.log.bz2 added |
---|
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 11 years ago by michaelld (Michael Dickens)
Any recommendation on how to blacklist correctly for this issue?
comment:3 Changed 11 years ago by michaelld (Michael Dickens)
Repeat of my question: Any recommendation on how to blacklist correctly for this issue?
comment:4 Changed 9 years ago by michaelld (Michael Dickens)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
No response, and, really, does this matter any longer? Closing as wontfix. If you disagree then reopen and provide some feedback. I can't test potential fixes, but I'm happy to incorporate a patch if someone creates one.
Replying to ryandesign@…:
The build succeeded on Leopard Intel also with gcc-4.2 build 5577. How strange. (The upstream bug report I mentioned was on Linux Intel.)