Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libpng: allow selection of older libpng versions
Date: Sun, 21 Jul 2019 15:49:28 +0200	[thread overview]
Message-ID: <20190721154928.11db1c4f@windsurf> (raw)
In-Reply-To: <20190707165224.31438-1-paul@crapouillou.net>

Hello Paul,

+Yann, Arnout, Peter in Cc.

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.
> 
> Signed-off-by: Paul Cercueil <paul@crapouillou.net>

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.

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

Best regards,

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

  reply	other threads:[~2019-07-21 13:49 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 [this message]
2019-07-21 14:22   ` Yann E. MORIN
2019-07-21 16:51     ` Paul Cercueil
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=20190721154928.11db1c4f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox