yate is marked for autoremoval from testing

[Paul Chitescu]

On Fri Jul 25, 2014 18:22:11 Tzafrir Cohen wrote:
> It takes longer than I have expected.
>
> On Fri, Jul 25, 2014 at 09:42:25AM +0300, Tzafrir Cohen wrote:
> > I did my best: a pending patch to #35733 (on debhelper).  Let me know
> > what you think.
> >
> > Also, if anybody has a comment on #737742 (basically: document yate in
> > https://wiki.debian.org/UnifiedCommunications/DebianDevelopers/UserGuide)
> >.
> >
> > For the record, here is the output of dh_shlibdeps:
>
> Actually I had to include them in the package as otherwise the upload is
> rejected.
>
> Another error I get from lintian:
>
> E: yate-dev: pkg-config-bad-directive
> usr/lib/x86_64-linux-gnu/pkgconfig/yate.pc -fPIC E: yate-dev:
> pkg-config-bad-directive usr/lib/x86_64-linux-gnu/pkgconfig/yate.pc
> -fno-check-new
>
> Why are -fPIC and -fno-check-new needed?

-fPIC is used because Yate modules are relocatable shared objects. Why does 
lintian complain about it?

-fno-check-new is set because -fcheck-new was default at some time (gcc 2 or 3 
or so). We could probably simply remove it from configure.in, especially since 
it appears to not be supported by clang.

Paul