All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/sunxi-mali: remove sunxi-mali r2p4 kernel module
Date: Sat, 18 Feb 2017 16:16:43 +0100	[thread overview]
Message-ID: <65b9e334-f4a3-cc8c-72eb-c2075dcbaf8a@gmail.com> (raw)
In-Reply-To: <20170218150549.GF3632@free.fr>

Yann, All,

Le 18/02/2017 ? 16:05, Yann E. MORIN a ?crit :
> Romain, All,
> 
> On 2017-02-18 15:52 +0100, Romain Naour spake thusly:
>> sunxi-mali r2p4 kernel module are linked against libUMP.so.2 but libump
>> package in Buildroot only provide libUMP.so.3, see [1].
> 
> OTOH, it looks like the versioning is just arbitrary:
> 
>     https://github.com/linux-sunxi/libump/commit/1c1f6337dffffe8f7aea98f710f681727ed45f4f
> 
>     We prefer version 3, as r2pX is pretty rare by now, but if needs be,
>     this can be easily changed.
> 
> So maybe libump could add a legacy symlink libUMP.so.2 -> libUMP.so.3 ?

Yes probably in this specific case but doing so is generally highly not
recommended :p
Also since r2pX was pretty rare back in 2013, I don't think it's a big loss.

Best regards,
Romain

> 
> Regards,
> Yann E. MORIN.
> 

  reply	other threads:[~2017-02-18 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18 14:52 [Buildroot] [PATCH 1/2] package/sunxi-mali: reorder select/depends Romain Naour
2017-02-18 14:52 ` [Buildroot] [PATCH 2/2] package/sunxi-mali: remove sunxi-mali r2p4 kernel module Romain Naour
2017-02-18 15:05   ` Yann E. MORIN
2017-02-18 15:16     ` Romain Naour [this message]
2017-02-20 21:52   ` Thomas Petazzoni
2017-02-20 22:33     ` Romain Naour
2017-02-20 21:50 ` [Buildroot] [PATCH 1/2] package/sunxi-mali: reorder select/depends Thomas Petazzoni

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=65b9e334-f4a3-cc8c-72eb-c2075dcbaf8a@gmail.com \
    --to=romain.naour@gmail.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.