Summary: | media-gfx/hugin: cmake-2.4.X fails to find wxwidgets while building hugin | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Johannes Spielmann <js> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log of the failed build
environment at compile time |
Description
Johannes Spielmann
2009-05-28 19:36:32 UTC
Created attachment 192746 [details]
build.log of the failed build
Created attachment 192748 [details]
environment at compile time
Note that #237653 is very similar and marked as resolved, did however not help in my case as I re-emerged both wxGTK and eselect-wxwidgets and the file /usr/bin/wx-config exists Does wx-config look like it works properly? For instance, what does 'wx-config --release' say? wx-config seems to be working (from my limited knowledge). Sample output: port ~ # wx-config --static port ~ # wx-config --libs -L/usr/local/lib -pthread -lwx_gtk-2.4 port ~ # wx-config --basename wx_gtk port ~ # wx-config --gl-libs -lwx_gtk_gl-2.4 -lGL -lGLU port ~ # wx-config --release 2.4 Hmm. That's strange. I'll replace it with the also-available wx-config-2.8 and try again... Ok, I found a workaround enabling the hugin compile. Here's the situation beforehand: /usr/local/bin/wx-config belongs to no package, but was apparently left over from wxGTK-1.4 /usr/bin/wx-config points to /usr/local/bin/wx-config /usr/bin/wx-config-2.8 is the current wx-config -- but was never called I tried removing /usr/local/bin/wx-config but then wx-config wouldn't work anymore. So I overwrote it with the real /usr/bin/wx-config. Afterwards everything worked how it should. So, how do I find out how the mixup happened and how can we prevent it from happening in the future and for other people? portage usually doesn't install any software into /usr/local/. So you either hit a buggy wxGTK-1.4 ebuild or you installed that file there by intention/accident. There's nothing we can do to help you tracking this down as long as the file doesn't belong to any package. Since this is no bug in our current wxGTK ebuilds, I gonna mark this bug as INVALID. |