Bug#876554: wrong pkgconfig files

2017-09-23 Thread Sven Joachim
On 2017-09-23 18:51 +0200, Bertrand Marc wrote:

> Package: src:libextractor
> Version: 1:1.3-2
> Severity: serious
>
> configure.ac messes up with user variables CFLAGS, CPPFLAGS, LIBS and
> LDFLAGS. Since these are used to generate pkgconfig files, the user
> flags are wrongly passed to
> libextractor.pc (see on Debian -D_FORTIFY_SOURCE=2).
>
> This generates the following lintian errors and therefore prevent any new 
> upload to unstable:
> libextractor-dev (1:1.3-4+b2; main)
>     E pkg-config-bad-directive
>     usr/lib/i386-linux-gnu/pkgconfig/libextractor.pc -D_FORTIFY_SOURCE=2
>     usr/lib/i386-linux-gnu/pkgconfig/libextractor.pc -Wdate-time
>     usr/lib/x86_64-linux-gnu/pkgconfig/libextractor.pc -D_FORTIFY_SOURCE=2
>     usr/lib/x86_64-linux-gnu/pkgconfig/libextractor.pc -Wdate-time
>
>
> This bug was reported upstream in November 2015, without success. Any help 
> solving this would be greatly appreciated.

It seems that libextractor uses outdated versions of autoconf macros,
especially m4/ax_create_pkgconfig_info.m4.  You could try to replace it
with the version from the autoconf-archive package, which should have
fixed the issue according to [1].

Cheers,
   Sven


1. 
http://git.savannah.nongnu.org/cgit/autoconf-archive.git/commit/m4/ax_create_pkgconfig_info.m4?id=b7f95244497a32f67f60ec16dabc665c05bab734



Bug#876554: wrong pkgconfig files

2017-09-23 Thread Bertrand Marc
Package: src:libextractor
Version: 1:1.3-2
Severity: serious

configure.ac messes up with user variables CFLAGS, CPPFLAGS, LIBS and LDFLAGS. 
Since these are used to generate pkgconfig files, the user flags are wrongly 
passed to
libextractor.pc (see on Debian -D_FORTIFY_SOURCE=2).

This generates the following lintian errors and therefore prevent any new 
upload to unstable:
libextractor-dev (1:1.3-4+b2; main)
    E pkg-config-bad-directive
    usr/lib/i386-linux-gnu/pkgconfig/libextractor.pc -D_FORTIFY_SOURCE=2
    usr/lib/i386-linux-gnu/pkgconfig/libextractor.pc -Wdate-time
    usr/lib/x86_64-linux-gnu/pkgconfig/libextractor.pc -D_FORTIFY_SOURCE=2
    usr/lib/x86_64-linux-gnu/pkgconfig/libextractor.pc -Wdate-time


This bug was reported upstream in November 2015, without success. Any help 
solving this would be greatly appreciated.