Summary: | subversion-1.0.8 fails - cannot find -lswigpy | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96 |
Component: | [OLD] Unspecified | Assignee: | Paul de Vrieze (RETIRED) <pauldv> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | gentoo+bugs, m.debruijne |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
f5d8fd51ed1e804c9e8d0357e8614e0493b06e96
2004-09-26 10:20:08 UTC
re-emerging 'swig', this time with the 'python' USE flag set solved the problem... for this time it built the python bindings that subversion was missing on the last try... but one question remains for me - why was subversion requiring those without the 'python' USE flag set? *** Bug 65424 has been marked as a duplicate of this bug. *** hmm... no, I were wrong.... the problem remains... Downgrading to swig-1.3.21 as I stated in http://bugs.gentoo.org/show_bug.cgi?id=65424 fixes the compile issues. I think the problem is caused by the removal of some runtime stuff from the swig ebuild/package. Which I also reported in said bug. So, why did mine get duped instead of this one? Harm, I commented on the original bug (which is not a duplicate indeed), and we will fix swig. In the meantime I'll try to check out why python is required when it shouldn't. Stale bug, reopen if this is still an issue with up-to-date subversion ebuilds. |