On Tue, Jan 09, 2018 at 11:13:11AM +, Hugh McMaster wrote:
> When I last checked, 33 packages FTBFS with freetype-config removed [1].
> That said, removing freetype-config was -- and still is -- my preferred
> option. See bug #870618 for the request.
I think I ran into ~6 of them (because
Hi Helmut,
On Monday, 8 January 2018 1:02 AM, Helmut Grohne wrote:
>> Hugh McMaster wrote:
>> Remember, freetype-config was never designed for cross-compiling.
>> So it's debatable whether we should (attempt to) support this.
> I agree. How about removing it from the package? It's not that many
>
On Sun, Jan 07, 2018 at 12:14:20PM +, Hugh McMaster wrote:
> On Saturday, 6 Jan 2018 11:59:23 +0100, Helmut Grohne wrote:
> Did you set PKG_CONFIG_LIBDIR to /usr/lib/i386-linux-gnu/pkgconfig?
No. One is not supposed to set PKG_CONFIG_LIBDIR as it breaks the cross
wrapper and thus breaks using
Hi Helmut,
On Saturday, 6 Jan 2018 11:59:23 +0100, Helmut Grohne wrote:
Did you set PKG_CONFIG_LIBDIR to /usr/lib/i386-linux-gnu/pkgconfig?
That aside, calling `freetype-config` or `pkg-config --libs freetype2` when
libfreetype6-dev is installed only for a foreign architecture does emit
those
Package: libfreetype6-dev
Version: 2.8.1-1
Severity: important
User: helm...@debian.org
Usertags: rebootstrap
If I "apt-get install libfreetype6-dev:i386 pkg-config" and then run
"freetype-config --cflags; echo $?", I get:o
In an i386 sid chroot:
$ freetype-config --cflags; echo $?
5 matches
Mail list logo