On Wed, Oct 7, 2015 at 7:40 AM, Antonio Cervone <ant.cerv...@gmail.com> wrote:
> this is due to a recent change in archlinux package, see > https://bugs.archlinux.org/task/46431 and > https://bugs.archlinux.org/task/43378 > I hope they will revert this change back, in the mean time check > > > https://github.com/capitalaslash/libmesh/commit/1fa8fc38944d719e8e7ada35bc345e21d94eeaca > > for a temporary workraound. > Thanks for the extra information, Antonio. I have been wondering why VTK went with this naming scheme, how distros would eventually handle it, and why on earth they don't provide some kind of "vtk-config --libs" script that would help out with the issue. Do you think it's worth trying to actually support the distros' alternate naming scheme in libmesh's m4 files? I don't think it would be too difficult. Other than Arch and Fedora, are there any others that do this? -- John ------------------------------------------------------------------------------ Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
