From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 2/4] package/celt051: needs dynamic library
Date: Fri, 24 Jan 2020 19:14:38 +0100 [thread overview]
Message-ID: <20200124181438.GD32369@scaer> (raw)
In-Reply-To: <069a1277-e9bc-c297-4da3-a89cd776c79c@mind.be>
Arnout, All,
On 2020-01-23 23:23 +0100, Arnout Vandecappelle spake thusly:
> On 23/11/2019 17:05, Fabrice Fontaine wrote:
> > Dear Peter,
> >
> > Le sam. 23 nov. 2019 ? 14:38, Peter Korsgaard <peter@korsgaard.com> a ?crit :
> >>
> >>>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> >>
> >> > celt051 can't be built statically with opus as opus embeds its own celt
> >> > version. So add a dynamic library dependency to celt051 (and not to
> >> > opus, as celt051 is only used optionally by spice whereas opus is
> >> > selected by 9 packages)
> [snip]
> >> Care to send a patch doing something like that? Thanks.
> > An other option would be to remove celt051 package indeed the root
> > cause of this static build failure is that celt has been merged into
> > the IETF Opus codec and is now obsolete (see http://celt-codec.org/).
>
> Indeed, that makes more sense. Care to remove it? Legacy handling should select
> BR2_PACKAGE_OPUS then (with appropriate explanation).
>
> Yann is developer for celt051, so please give a peep if it can't be removed.
Well, celt-0.51 was introduced because at the time. spice on;y supported
that, and not the later versions, which is still documented in the
package itself.
But sicne then (7 years ago now), spice was updated, so maybe it can
support newer versions, and maybe it works with Opus instead.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-01-24 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 16:44 [Buildroot] [PATCH v2,1/4] package/spice: disable tests Fabrice Fontaine
2019-11-17 16:44 ` [Buildroot] [PATCH v2,2/4] package/celt051: needs dynamic library Fabrice Fontaine
2019-11-23 13:38 ` [Buildroot] [PATCH v2, 2/4] " Peter Korsgaard
2019-11-23 16:05 ` Fabrice Fontaine
2020-01-23 22:23 ` Arnout Vandecappelle
2020-01-24 18:14 ` Yann E. MORIN [this message]
2020-01-27 16:22 ` Arnout Vandecappelle
2020-01-27 16:25 ` Fabrice Fontaine
2019-11-17 16:44 ` [Buildroot] [PATCH v2, 3/4] package/spice-protocol: bump to version 0.14.0 Fabrice Fontaine
2019-11-23 13:33 ` Peter Korsgaard
2019-12-03 9:49 ` Peter Korsgaard
2019-12-03 10:08 ` Baruch Siach
2019-12-03 12:15 ` Peter Korsgaard
2019-11-17 16:44 ` [Buildroot] [PATCH v2, 4/4] package/spice: security bump to version 0.14.2 Fabrice Fontaine
2019-11-23 13:33 ` Peter Korsgaard
2019-12-03 9:49 ` Peter Korsgaard
2019-11-18 21:47 ` [Buildroot] [PATCH v2,1/4] package/spice: disable tests Thomas Petazzoni
2019-11-19 7:47 ` Fabrice Fontaine
2019-11-19 8:15 ` Thomas Petazzoni
2019-11-22 22:14 ` Peter Korsgaard
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=20200124181438.GD32369@scaer \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox