Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Giulio Benetti
Il 17/10/2018 21:48, Hendrik Leppkes ha scritto: On Wed, Oct 17, 2018 at 9:45 PM Moritz Barsnick wrote: On Wed, Oct 17, 2018 at 21:40:58 +0200, Giulio Benetti wrote: PS: do I need to remove your e-mail on TO field every time I reply to you? It's not a problem, only to know. This mailing lis

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Giulio Benetti
Il 17/10/2018 21:45, Moritz Barsnick ha scritto: On Wed, Oct 17, 2018 at 21:40:58 +0200, Giulio Benetti wrote: PS: do I need to remove your e-mail on TO field every time I reply to you? It's not a problem, only to know. This mailing list uses a Reply-To: header, pointing at the list address. Y

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Hendrik Leppkes
On Wed, Oct 17, 2018 at 9:45 PM Moritz Barsnick wrote: > > On Wed, Oct 17, 2018 at 21:40:58 +0200, Giulio Benetti wrote: > > PS: do I need to remove your e-mail on TO field every time I reply to > > you? It's not a problem, only to know. > > This mailing list uses a Reply-To: header, pointing at t

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Moritz Barsnick
On Wed, Oct 17, 2018 at 21:40:58 +0200, Giulio Benetti wrote: > PS: do I need to remove your e-mail on TO field every time I reply to > you? It's not a problem, only to know. This mailing list uses a Reply-To: header, pointing at the list address. Your Thuderbird should honor that automatically (

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Giulio Benetti
Il 17/10/2018 21:23, Carl Eugen Hoyos ha scritto: 2018-10-17 21:20 GMT+02:00, Giulio Benetti : Il 17/10/2018 18:51, Carl Eugen Hoyos ha scritto: I just meant that it was a mistake that above patch was backported although it neither fixes a security issue nor a regression. Ok, I understand, so

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Carl Eugen Hoyos
2018-10-17 21:20 GMT+02:00, Giulio Benetti : > Il 17/10/2018 18:51, Carl Eugen Hoyos ha scritto: >> I just meant that it was a mistake that above patch was backported >> although it neither fixes a security issue nor a regression. > > Ok, I understand, so please discard this patch. I was under the

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Giulio Benetti
Il 17/10/2018 18:51, Carl Eugen Hoyos ha scritto: I just meant that it was a mistake that above patch was backported although it neither fixes a security issue nor a regression. Ok, I understand, so please discard this patch. On Buildroot we will use a not upstreamed patch then. Please don't

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Carl Eugen Hoyos
2018-10-17 15:54 GMT+02:00, Giulio Benetti : > Re-add everybody in Cc > > Il 17/10/2018 15:08, Carl Eugen Hoyos ha scritto: >> 2018-10-17 14:02 GMT+02:00, Giulio Benetti >> : >>> Commit c50dc77ac708e98d02da7c422a6b9cbf9f565aa5 has a pitfall, it >>> appends -ldrm to "Libs:" instead of "Libs.private:

Re: [FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Giulio Benetti
Re-add everybody in Cc Il 17/10/2018 15:08, Carl Eugen Hoyos ha scritto: 2018-10-17 14:02 GMT+02:00, Giulio Benetti : Commit c50dc77ac708e98d02da7c422a6b9cbf9f565aa5 has a pitfall, it appends -ldrm to "Libs:" instead of "Libs.private:" in avutil.pc. Assuming this was not a regression before:

[FFmpeg-devel] [PATCH 3.4 0/2] configure: fix LIBDRM handling for static linking

2018-10-17 Thread Giulio Benetti
Commit c50dc77ac708e98d02da7c422a6b9cbf9f565aa5 has a pitfall, it appends -ldrm to "Libs:" instead of "Libs.private:" in avutil.pc. This leads to append -ldrm to link library list tail in shared build too and this doesn't make sense. So revert the commit above and add a patch to handle explicit pri