| Summary: | net-im/twinkle works on amd64 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Karol Krizka <kkrizka> |
| Component: | New packages | Assignee: | AMD64 Project <amd64> |
| Status: | RESOLVED LATER | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Karol Krizka
2005-10-15 23:40:37 UTC
Latest twinkle does not build out of the box with GCC4 because of a pointer -> integer cast, so I don't really think it's safe to mark it without patch (also if it's a safe cast, just for logging). Worse, ccrtp (dependency of this) is using a pointer -> uint32 cast that *is* dangerous. I'm submitting a new bug with the two needed patches, I'll mark it after a bit of testing when those are applied. But on amd64 GCC4 is still hardmasked. So it shouldn't matter. It can be hardmasked as you like, but the problem is not that GCC4 bitches, it's that GCC3 leave you through broken code. Try casting a pointer to uint32 and then take it back and use it as a pointer, you'll see interesting things many times :P Anyway, see bug #110856 |
