Summary: | dev-haskell/wxhaskell-0.8-r1 ebuild fails on amd64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gour <gour> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ge, kosmikus |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gour
2004-11-26 03:09:59 UTC
Afaics, the -m32 is the culprit. Now I don't know enough about gcc or amd64 to judge if -m32 is a valid choice for CXXFLAGS. I can modify the ebuild to use strip-flags, which if I interpret flag-o-matics.eclass correctly, will get rid of -m32 on amd64. Gour, you should be fine by compiling wxhaskell with -m32 removed. Can someone provide input if strip-flags is the way to go, or if something else should be done? Cheers, ks Hi Kosmikus!
>Gour, you should be fine by compiling wxhaskell with -m32 removed.
>Can someone provide input if strip-flags is the way to go, or if
>something else should be done?
Pls. excuse me for a false alarm :-(
The problem is that I tried to compile wxhaskell in the wron konsole, i.e. the one where I was experimenting in compiling clisp with some modules for xindy indexing packages and there I went with very light flags :-)
Now, wxhaskell is happy compiling and it emerged fine, so I'll close a bug.
Sincerely,
Gour
|