On Fri, Jun 24, 2011 at 8:11 AM, Andreas Tille <[email protected]> wrote: >> So you can reassign your bug where it belongs (libvtk5-dev). Unfortunately, >> VTK >> has one of the most hackish (and outdated in places) cmake code. Good luck >> fixing it. > > Thanks for your analysis. I have just no idea of cmake and obviosely > had no idea where to look at after I have seen that old cmake in testing > worked and cmake in unstable did not. The hint about multiarch stuff > added in unstable seemed like a reasonable explanation at first sight. > So thanks for enlighting the reasons.
Thanks Modestas for finding the reason. I started a long time ago fixing VTK to remove the culprit call to EXPORT_LIBRARY_DEPENDENCIES, but had to give up. I could not get it apply upstream, maybe we can resurect this patch in debian/VTK: https://github.com/malaterre/VTK/commit/07db5b4fd2477f3843e6726ea5011aa2540921ab 2cts -- Mathieu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
