[Bug 805213] [NEW] AvogadroLibraryDeps.cmake has wrong path to libGLU.so

Launchpad Bug Tracker 805213 at bugs.launchpad.net
Sun Jul 3 19:23:26 UTC 2011

You have been subscribed to a public bug by Philip Muškovac (yofel):

AvogadroLibraryDeps.cmake has /usr/lib/libGLU.so in _LIB_DEPENDS. Now
that mesa uses multiarch the file is now in /usr/lib/x86_64-linux-
gnu/libGLU.so (amd64). This causes a build failure in kalzium 4.6.90:

make[2]: Entering directory `/tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu'
cd /tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /tmp/buildd/kalzium-4.6.90+repack /tmp/buildd/kalzium-4.6.90+repack/compoundviewer /tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu /tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu/compoundviewer /tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu/compoundviewer/CMakeFiles/compoundviewer.dir/DependInfo.cmake --color=
make[2]: Leaving directory `/tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu'
make -f compoundviewer/CMakeFiles/compoundviewer.dir/build.make compoundviewer/CMakeFiles/compoundviewer.dir/build
make[2]: Entering directory `/tmp/buildd/kalzium-4.6.90+repack/obj-x86_64-linux-gnu'
make[2]: *** No rule to make target `/usr/lib/libGLU.so', needed by `lib/libcompoundviewer.so.4.7.0'.  Stop.

A rebuild of avogadro sets the right path.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libavogadro-dev 1.0.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Jul  3 21:12:58 2011
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
 PATH=(custom, user)
SourcePackage: avogadro
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: avogadro (Ubuntu)
     Importance: High
         Status: Triaged

** Tags: amd64 apport-bug multiarch oneiric
AvogadroLibraryDeps.cmake has wrong path to libGLU.so
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.

More information about the Ubuntu-sponsors mailing list