On Fri, Jun 12, 2020 at 02:59:40AM +0200, Kamil Rytarowski wrote: > On 12.06.2020 02:07, Joerg Sonnenberger wrote: > > On Fri, Jun 12, 2020 at 01:28:15AM +0200, Kamil Rytarowski wrote: > >> Please list legitimate false positives. There is practically nothing > >> like that possible for using deprecated APIs (at least kept longer > >> term). Besides that, the report shall be lowered to warning (like it > >> used to be for Clang). > > > > Build a random KDE package and see warnings about XHR symbols? > > > > Joerg > > > > XDR? > > $ grep -ir xdr .|grep warn > ./libc/yp/xdryp.c:__warn_references(xdr_domainname, > ./libc/yp/xdryp.c: "warning: this program uses xdr_domainname(), > which is deprecated and buggy.") > ./libc/yp/xdryp.c:__warn_references(xdr_peername, > ./libc/yp/xdryp.c: "warning: this program uses xdr_peername(), which > is deprecated and buggy.") > ./libc/yp/xdryp.c:__warn_references(xdr_mapname, > ./libc/yp/xdryp.c: "warning: this program uses xdr_mapname(), which > is deprecated and buggy.") > > KDE4?
No, KDE5. > > After grepping, I don't see relevant users of these APIs. There is > something around Python that has a NIS/YP module. Exactly, nothing in Qt uses it, but it *still* triggers the warning. Joerg