Summary: | avifile (avifile-0.7.32.20030219) doesn't build; reports unknown symbols in libXft | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ray Heasman <gbugs> |
Component: | [OLD] Library | Assignee: | foser (RETIRED) <foser> |
Status: | VERIFIED FIXED | ||
Severity: | major | CC: | x11 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ray Heasman
2003-07-08 11:04:42 UTC
reemerge x11-libs/xft then go on Thanks for the suggestion. This is what happens. --- maze portage # emerge xft Calculating dependencies ...done! !!! Error: the >=x11-base/xfree-4.3.0-r2 package conflicts with this package and both can't be installed on the same system together. --- Huh? I can't have XFT installed when I use X? Will I be able to "emerge --resume" my rebuild after emerging stuff manually? please check your xfree version later xfree provides xft since it got incorporated in the xfree tree and developed/improved there please emerge fontconfig too. Thanks for the suggestion. Re-emerging fontconfig made the difference. I had xfree 4.3.0-r2, and fontconfig 2.2.0-r2 installed. Re-emerging fontconfig 2.2.0-r2 made avifile build successfully. I didnt touch xfree. I really have no idea why. Perhaps fontconfig was still GCC2-compiled code? Perhaps portage tried to compile avifile before it got around to compiling fontconfig. I think that fontconfig got pruned during the xft changes. closing the bug. I emerged the SAME version of fontconfig. No emerge sync, no update. The only thing changed was that it MIGHT have been previously compiled with GCC2 rather than GCC3. I don't know how the portage stuff works, so I'll leave the conclusions up to you. :-) Thanks for the help. Just an additional note about this.. I ran across this same issue and tried re-emerging fontconfig without any luck. As it turns out, I had xft-2.0.1-r2 emerged with xfree-4.3.0-r2 (xft showed a block but xfree didnt). Probably a leftover from running xfree-4.2.99. Solution was to `emerge unmerge xft` then `emerge xfree fontconfig avifile`. Perhaps xft should be masked now that the stable xfree installs it? The block was obvious when trying to `emerge xft` but xfree would emerge with xft without a complaint. you are on to something here. The xfree ebuild mistakenly blocks virtual/xft, while this doesn't work at this time (should it ever?). I've changed the block to x11-libs/xft now, which should properly block out the xft ebuild. xfree team members please take a mental note of this. thanks for your comment on this lanalyst. it works with the virtual/mta ebuilds it was a portage issue -- the new -r7 release of portage should recognise blocks again. Well, -r5 and -r6 don't and i think most people are running that. Did it work before those versions ? Cause it had been virtual/xft for quite some time. Anyway, if the current setup works with all portage versions i think its better this way for now (practical, not esthetical), since there are only 2 xft providers. |