Bug#779282: libitpp-dev: Bad information in itpp.pc
tags 779282 + confirmed thanks On Fri, Feb 27, 2015 at 11:21:17AM +0100, Serrière Guillaume wrote: Hi, Thanks for the fast answer :). There is no symbolic link in /usr/lib/ The symbolic link is also install in the package is in /usr/lib/x86_64-linux-gnu. /usr/lib$ ls -all | grep itpp /usr/lib$ ls -all x86_64-linux-gnu/ | grep itpp lrwxrwxrwx 1 root root 12 Mar 22 2014 libitpp.so - libitpp.so.8 lrwxrwxrwx 1 root root 16 Mar 22 2014 libitpp.so.8 - libitpp.so.8.2.1 -rw-r--r-- 1 root root 4010536 Mar 22 2014 libitpp.so.8.2.1 For other libraries we use that are in the same case (multi-arch support) the pkg-config libdir variable indicates the path to the x86_64-gnu-linux directory (gtk2+, ogre, ...). Indeed, this is correct. I will fix it in an upload in the next week. Thanks. Kumar -- Kumar Appaiah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779282: libitpp-dev: Bad information in itpp.pc
Hi, Thanks for the fast answer :). There is no symbolic link in /usr/lib/ The symbolic link is also install in the package is in /usr/lib/x86_64-linux-gnu. /usr/lib$ ls -all | grep itpp /usr/lib$ ls -all x86_64-linux-gnu/ | grep itpp lrwxrwxrwx 1 root root 12 Mar 22 2014 libitpp.so - libitpp.so.8 lrwxrwxrwx 1 root root 16 Mar 22 2014 libitpp.so.8 - libitpp.so.8.2.1 -rw-r--r-- 1 root root 4010536 Mar 22 2014 libitpp.so.8.2.1 For other libraries we use that are in the same case (multi-arch support) the pkg-config libdir variable indicates the path to the x86_64-gnu-linux directory (gtk2+, ogre, ...). Guillaume On 27/02/2015 02:16, Kumar Appaiah wrote: Hi. On Thu, Feb 26, 2015 at 03:48:52PM +0100, Guillaume Serrière wrote: Package: libitpp-dev Version: 4.3.1-3 Severity: normal Dear Maintainer, I'm a developper on the OpenViBE project which use the itpp library. During the compilation, we use pkg-config to get the path to libraries we use to make the linkage of our plugins. In Jessie, the libitpp.so is install under /usr/lib/x86_64-linux-gnu, however, we get the following stuff: $ pkg-config --variable=libdir itpp /usr/lib This command should return the right path to the library (/usr/lib/x86_64-linux-gnu). Thanks for the bug report. Indeed, it prints out /usr/lib, but that is where a symbolic link lies to the actual library. So, if you use the pkg-config libdir to link, you will be successful. Using the pkg-config directory to find out where to install is not a good idea, IMHO. The x86_64-linux-gnu is a side-effect of multiarch, so you might have to use the same multiarch approach if your plugins are libraries, so that they are moved to the right directory during the install process. Please let me know if I can help further, or I have misunderstood something. Thanks. Kumar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779282: libitpp-dev: Bad information in itpp.pc
You make my day, thank you very much. Guillaume On 27/02/2015 12:02, Kumar Appaiah wrote: tags 779282 + confirmed thanks On Fri, Feb 27, 2015 at 11:21:17AM +0100, Serrière Guillaume wrote: Hi, Thanks for the fast answer :). There is no symbolic link in /usr/lib/ The symbolic link is also install in the package is in /usr/lib/x86_64-linux-gnu. /usr/lib$ ls -all | grep itpp /usr/lib$ ls -all x86_64-linux-gnu/ | grep itpp lrwxrwxrwx 1 root root 12 Mar 22 2014 libitpp.so - libitpp.so.8 lrwxrwxrwx 1 root root 16 Mar 22 2014 libitpp.so.8 - libitpp.so.8.2.1 -rw-r--r-- 1 root root 4010536 Mar 22 2014 libitpp.so.8.2.1 For other libraries we use that are in the same case (multi-arch support) the pkg-config libdir variable indicates the path to the x86_64-gnu-linux directory (gtk2+, ogre, ...). Indeed, this is correct. I will fix it in an upload in the next week. Thanks. Kumar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779282: libitpp-dev: Bad information in itpp.pc
Package: libitpp-dev Version: 4.3.1-3 Severity: normal Dear Maintainer, I'm a developper on the OpenViBE project which use the itpp library. During the compilation, we use pkg-config to get the path to libraries we use to make the linkage of our plugins. In Jessie, the libitpp.so is install under /usr/lib/x86_64-linux-gnu, however, we get the following stuff: $ pkg-config --variable=libdir itpp /usr/lib This command should return the right path to the library (/usr/lib/x86_64-linux-gnu). *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libitpp-dev depends on: ii libitpp8 4.3.1-3 libitpp-dev recommends no packages. libitpp-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779282: libitpp-dev: Bad information in itpp.pc
Hi. On Thu, Feb 26, 2015 at 03:48:52PM +0100, Guillaume Serrière wrote: Package: libitpp-dev Version: 4.3.1-3 Severity: normal Dear Maintainer, I'm a developper on the OpenViBE project which use the itpp library. During the compilation, we use pkg-config to get the path to libraries we use to make the linkage of our plugins. In Jessie, the libitpp.so is install under /usr/lib/x86_64-linux-gnu, however, we get the following stuff: $ pkg-config --variable=libdir itpp /usr/lib This command should return the right path to the library (/usr/lib/x86_64-linux-gnu). Thanks for the bug report. Indeed, it prints out /usr/lib, but that is where a symbolic link lies to the actual library. So, if you use the pkg-config libdir to link, you will be successful. Using the pkg-config directory to find out where to install is not a good idea, IMHO. The x86_64-linux-gnu is a side-effect of multiarch, so you might have to use the same multiarch approach if your plugins are libraries, so that they are moved to the right directory during the install process. Please let me know if I can help further, or I have misunderstood something. Thanks. Kumar -- Kumar Appaiah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
