Summary: | gvim-6.2-r3 compile error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcus J. van Dijk, Jr. <tratz> |
Component: | [OLD] Unspecified | Assignee: | Vim Maintainers <vim> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output of gvim emerge
etcat -u dev-lang/python |
Description
Marcus J. van Dijk, Jr.
2003-10-31 12:01:57 UTC
Please attach output of emerge info, and output of "etcat -u dev-lang/python" (you might need to emerge gentoolkit to get etcat). Thanks Created attachment 20131 [details]
output of gvim emerge
Created attachment 20132 [details]
etcat -u dev-lang/python
Okay, something strange here... The vim configure doesn't believe that you have ANSI C headers. On my system this works fine. You haven't posted the output of "emerge info". Sorry if my request for that was unclear. I see that you're using some serious CFLAGS there. Makes me pretty suspcious actually. How about doing CFLAGS="-march=athlon-xp -O3 -pipe" emerge python gvim I'd like to make sure that isn't the problem before proceeding to debug this further. If you intend to use such souped-up CFLAGS, it's really helpful if you're able to do some debugging yourself. A lot of Gentoo bugs come down to overcooked CFLAGS. Mark, any results? Slipped my mind Aron, my apoligies. I forgot all about those cflags, shame on me. It works nicely now with the default CFlags. I will mark it as invalid because seemingly it is not really a bug. Cool, thanks |