All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ffmpeg: fix static linking build failure when using libavutil
Date: Mon, 24 Sep 2018 13:09:29 +0200	[thread overview]
Message-ID: <20180924130929.4b345624@windsurf> (raw)
In-Reply-To: <63ee101c-ee45-57cc-4aeb-7f3b49753ccb@micronovasrl.com>

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?

Both ? :-)

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-24 11:09 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 [this message]
2018-09-24 11:11       ` Giulio Benetti
2018-10-12 17:38         ` Giulio Benetti
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=20180924130929.4b345624@windsurf \
    --to=thomas.petazzoni@bootlin.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.