From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Patches I Use [3] - ldconfig -N opt
Date: Tue, 9 Nov 2010 18:39:36 +0100 [thread overview]
Message-ID: <20101109183936.41a980a0@surf> (raw)
In-Reply-To: <1289317856.30565.115.camel@tr-pentomino>
On Tue, 09 Nov 2010 07:50:56 -0800
Darcy Watkins <dwatkins@tranzeo.com> wrote:
> This instructs the ldconfig not to build / rebuild the cache. It was
> a while back I encountered this and I have just carried it forward
> since. Someone more expert should check this and decide on its
> appropriateness for 2010.11 and/or future buildroot release.
Well all the point of calling ldconfig at this point is to create this
cache. So if we add -N to disable the cache build, what's the point of
calling ldconfig at all ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-11-09 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 15:50 [Buildroot] Buildroot Patches I Use [3] - ldconfig -N opt Darcy Watkins
2010-11-09 17:39 ` Thomas Petazzoni [this message]
2010-11-09 18:37 ` Darcy Watkins
2010-11-09 18:54 ` Thomas Petazzoni
2010-11-09 20:00 ` Darcy Watkins
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=20101109183936.41a980a0@surf \
--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