Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libpng: allow selection of older libpng versions
Date: Sun, 21 Jul 2019 12:51:44 -0400	[thread overview]
Message-ID: <1563727904.1774.0@crapouillou.net> (raw)
In-Reply-To: <20190721142245.GA17009@scaer>



Le dim. 21 juil. 2019 ? 10:22, "Yann E. MORIN" 
<yann.morin.1998@free.fr> a ?crit :
> Thomas, Paul, Al,
> 
> On 2019-07-21 15:49 +0200, Thomas Petazzoni spake thusly:
>>  On Sun,  7 Jul 2019 12:52:24 -0400
>>  Paul Cercueil <paul@crapouillou.net> wrote:
>>  > By allowing building an older version of libpng, we can create 
>> Buildroot
>>  > systems that are still binary-compatible with applications 
>> compiled with
>>  > older Buildroot toolchains.
>>  While I understand what you're trying to do, I'm not sure it's a
>>  reasonable goal for Buildroot to be able to provide binary
>>  compatibility between systems generated by different Buildroot
>>  versions. We regularly update libraries to their latest upstream
>>  versions, and sometimes they break the ABI compatibility. I don't 
>> think
>>  we want to enter the game of ensuring that ABI compatibility is 
>> ensured
>>  between Buildroot versions.
> 
> Agreed.

Honestly, in our case the only thing needed to support apps compiled 
with Buildroot 2014.05 with the new Buildroot 2019.02.1 is this patch, 
and a few symlinks in /lib (since libm/librt/etc. are gone). 
Thanksfully the major version of libraries doesn't change that often.


>>  If you're building a program with a given Buildroot SDK, it should 
>> be
>>  executed on the Buildroot system that matches that SDK.
> 
> Agreed.

Then that means we're stuck with a 2014.05 Buildroot and cannot 
contribute to upstream Buildroot development. It's not ideal.


> 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.  |
> '------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-07-21 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 16:52 [Buildroot] [PATCH 1/1] package/libpng: allow selection of older libpng versions Paul Cercueil
2019-07-21 13:49 ` Thomas Petazzoni
2019-07-21 14:22   ` Yann E. MORIN
2019-07-21 16:51     ` Paul Cercueil [this message]
2019-07-21 17:15       ` Yann E. MORIN

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=1563727904.1774.0@crapouillou.net \
    --to=paul@crapouillou.net \
    --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