All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@micronovasrl.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: fix static linking build failure when using libavutil
Date: Fri, 12 Oct 2018 19:38:14 +0200	[thread overview]
Message-ID: <8fb396bf-456c-2385-8fd0-84cbd4142e56@micronovasrl.com> (raw)
In-Reply-To: <1b5dece6-8730-89d4-53dc-44f3492c49d9@micronovasrl.com>

Hello Thomas,

Il 24/09/2018 13:11, Giulio Benetti ha scritto:
> Il 24/09/2018 13:09, Thomas Petazzoni ha scritto:
>> Hello,
>>
>> On Mon, 24 Sep 2018 12:26:05 +0200, Giulio Benetti wrote:
>>
>>>> Indeed, when we're dynamic linking, there is no need to link consumers
>>>> of libavutil with libdrm. It is only when we're statically linking that
>>>> it should be done. And that's exactly what Libs vs. Libs.private is for.
>>>
>>> You've explained me it very well, but by now FFmpeg upstreamed my patch:
>>> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/c50dc77ac708e98d02da7c422a6b9cbf9f565aa5
>>>
>>> So, do I rework and resubmit to them or can I re-create a patch for BR
>>> with what you've pointed me above?
I've missed one thing to ask you about ffmpeg:
Can I still use this hack:
https://git.ffmpeg.org/gitweb/ffmpeg.git/blobdiff/bc2301429e9c779237e43acf913331af018211f2..c50dc77ac708e98d02da7c422a6b9cbf9f565aa5:/configure

to obtain if -ldrm is used and then add it to Libs.private like this:
Libs.private: -ldrm

as you've pointed me.

Or there is something that makes it simpler and better?

Thanks in advance
Best regards
-- 
Giulio Benetti
CTO

MICRONOVA SRL
Sede: Via A. Niedda 3 - 35010 Vigonza (PD)
Tel. 049/8931563 - Fax 049/8931346
Cod.Fiscale - P.IVA 02663420285
Capitale Sociale ? 26.000 i.v.
Iscritta al Reg. Imprese di Padova N. 02663420285
Numero R.E.A. 258642

  reply	other threads:[~2018-10-12 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 20:42 [Buildroot] [PATCH] ffmpeg: fix static linking build failure when using libavutil Giulio Benetti
2018-09-11 21:47 ` Giulio Benetti
2018-09-13  8:15   ` Giulio Benetti
2018-09-16 20:22 ` Thomas Petazzoni
2018-09-24 10:26   ` Giulio Benetti
2018-09-24 11:09     ` Thomas Petazzoni
2018-09-24 11:11       ` Giulio Benetti
2018-10-12 17:38         ` Giulio Benetti [this message]
2018-10-12 19:50           ` Thomas Petazzoni
2018-10-12 20:54             ` Giulio Benetti
2018-10-16 19:31               ` Giulio Benetti
2018-10-17 10:36                 ` Giulio Benetti
2018-10-17 12:37                   ` [Buildroot] [PATCH v2] " Giulio Benetti
2018-10-17 12:39                     ` Giulio Benetti
2018-10-17 12:49                       ` [Buildroot] [PATCH v3] " Giulio Benetti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8fb396bf-456c-2385-8fd0-84cbd4142e56@micronovasrl.com \
    --to=giulio.benetti@micronovasrl.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.