Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Makefile: drop ldconfig handling
Date: Fri, 1 Jan 2016 21:58:10 +0100	[thread overview]
Message-ID: <20160101215810.77c4a518@free-electrons.com> (raw)
In-Reply-To: <20151231180135.GH3495@free.fr>

Yann,

On Thu, 31 Dec 2015 19:01:35 +0100, Yann E. MORIN wrote:

> I disagree on that one.
> 
> We basically tell user that they can do "whatever they want" in a
> post-build-script. So, if a user has a mean to create the ld.so.cache,
> we should not prevent him to do so.
> 
> For example, a user may have a first-install procedure on his machine,
> that runs ldocnfig natively on the machine. Custom (aka br2-external
> packages may install libraries in weird locations (proprietary stuff)
> and can not change that (because other proprietary binary-only stuff).
> In this vase a "first-install" procedure may run ldconfig natively on
> the target, and that would be OK.
> 
> Or he may have a cross-ldconfig (from wherever that comes) so he could
> run that in a post-build script.
> 
> So I believe this check should be before the overlay and post-build
> scripts.

You're absolutely right I believe. We should leave as much freedom as
possible for people to do what they want in their rootfs overlay and
post build scripts. I'll resend an updated version of my patch.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-01-01 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 14:48 [Buildroot] [PATCH v2] Makefile: drop ldconfig handling Thomas Petazzoni
2015-12-31 18:01 ` Yann E. MORIN
2016-01-01 20:58   ` Thomas Petazzoni [this message]

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=20160101215810.77c4a518@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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