Bug#947247: libcln-dev: move cln.pc to a multiarch location

2020-01-05 Thread Richard B. Kreckel
Hi Helmut, On 02.01.20 20:14, Helmut Grohne wrote: > Yes. I often opt for moving all components to the multiarch libdir. > However in the case of cln, the comment in debian/rules line 70 made me > not go that route: > > # This installs into libdir, but we must not set libdir because it affects

Bug#947247: libcln-dev: move cln.pc to a multiarch location

2020-01-02 Thread Helmut Grohne
Hi richy, On Wed, Jan 01, 2020 at 09:58:20PM +0100, Richard B. Kreckel wrote: > Hmmm, I have a question: Wouldn't it be more consistent to set $(libdir) > to /usr/lib//, so the library files are installed there, too, > not in /usr/lib/? Yes. I often opt for moving all components to the multiarch

Bug#947247: libcln-dev: move cln.pc to a multiarch location

2020-01-01 Thread Richard B. Kreckel
On 23.12.19 15:18, Helmut Grohne wrote: > ginac fails to cross build from source, because it cannot find cln.pc > using pkg-config. During cross compilation, pkg-config does not search > /usr/lib/pkgconfig. It only searches /usr/share/pkgconfig and > /usr/lib//pkgconfig. To be usable for cross

Bug#947247: libcln-dev: move cln.pc to a multiarch location

2019-12-23 Thread Helmut Grohne
Package: libcln-dev Version: 1.3.6-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs Control: affects -1 + src:ginac ginac fails to cross build from source, because it cannot find cln.pc using pkg-config. During cross compilation, pkg-config does not search /usr/lib/pkgconfig. It