Re: rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

2019-02-12 Thread Marcel Plch
On Tue, 2019-02-12 at 15:52 +0100, Florian Weimer wrote: > * Marcel Plch: > > > So rather than: > > "Python extension modules don't need to be linked against libc as > > they > > are never actually loaded on their own, but rather from the Python > >

Re: rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

2019-02-12 Thread Marcel Plch
On Tue, 2019-02-12 at 15:35 +0100, Florian Weimer wrote: > * Marcel Plch: > > > On Mon, 2019-02-11 at 18:47 +0100, Florian Weimer wrote > > > If you take the address of a local variable and pass the > > > resulting > > > pointer to another functio

Re: rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

2019-02-12 Thread Marcel Plch
On Mon, 2019-02-11 at 18:47 +0100, Florian Weimer wrote > If you take the address of a local variable and pass the resulting > pointer to another function, the compiler will generate a call to > __stack_chk_fail, which lives in glibc. At build time, linking > against > glibc is required so that th

Re: rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

2019-02-11 Thread Marcel Plch
n you please come up with a specific scenario, even better an example, where the problem occurs? Thank you, Marcel Plch ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Co