From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/6] rootfs.py: Check for LDCONFIGDEPEND being empty string
Date: Tue, 18 Feb 2014 10:37:08 +0200 [thread overview]
Message-ID: <20140218083708.GQ10078@lpalcu-linux> (raw)
In-Reply-To: <af841644dfc682e9774287331ef39c3cd1ede978.1392665521.git.raj.khem@gmail.com>
Hi Khem,
On Mon, Feb 17, 2014 at 11:34:15AM -0800, Khem Raj wrote:
> We override LDCONFIGDEPEND to be empty string for uclibc
> however the current check is for it being None as a result
> the function is still executed but ldconfig-native is not
> built as dependency for rootfs when building with uclibc
>
> Fixes errors like below
>
> File:
> '/home/kraj/work/angstrom-repo/sources/openembedded-core/meta/lib/oe/rootfs.py',
> lineno: 191, function: _run_ldconfig
> 0187: def _run_ldconfig(self):
> 0188: if self.d.getVar('LDCONFIGDEPEND', True) is not None:
> 0189: bb.note("Executing: ldconfig -r" +
> self.image_rootfs + "-c new -v")
> 0190: self._exec_shell_cmd(['ldconfig', '-r',
> self.image_rootfs, '-c',
> *** 0191: 'new', '-v'])
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/lib/oe/rootfs.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py
> index d149ca3..3bcb812 100644
> --- a/meta/lib/oe/rootfs.py
> +++ b/meta/lib/oe/rootfs.py
> @@ -185,7 +185,7 @@ class Rootfs(object):
> self._handle_intercept_failure(registered_pkgs)
>
> def _run_ldconfig(self):
> - if self.d.getVar('LDCONFIGDEPEND', True) is not None:
> + if self.d.getVar('LDCONFIGDEPEND', True) != "":
May I suggest:
if (self.d.getVar('LDCONFIGDEPEND', True) or "") != "":
here? Otherwise, the condition will be true even if LDCONFIGDEPEND is
None.
laurentiu
> bb.note("Executing: ldconfig -r" + self.image_rootfs + "-c new -v")
> self._exec_shell_cmd(['ldconfig', '-r', self.image_rootfs, '-c',
> 'new', '-v'])
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2014-02-18 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 19:33 [PATCH 0/6] eglibc upgrade 2.19, uclibc upgrade and fixes Khem Raj
2014-02-17 19:34 ` [PATCH 1/6] eglibc: Upgrade from 2.18 -> 2.19 Khem Raj
2014-02-17 19:34 ` [PATCH 2/6] valgrind: Add glibc 2.19 awareness Khem Raj
2014-02-17 19:34 ` [PATCH 3/6] rootfs.py: Check for LDCONFIGDEPEND being empty string Khem Raj
2014-02-18 8:37 ` Laurentiu Palcu [this message]
2014-02-18 8:48 ` Richard Purdie
2014-02-18 14:23 ` Khem Raj
2014-02-17 19:34 ` [PATCH 4/6] icu: Disable the default LDFLAGSICUDT for target compile Khem Raj
2014-02-17 21:53 ` Richard Purdie
2014-02-18 0:10 ` Khem Raj
2014-02-17 19:34 ` [PATCH 5/6] binutils: ld-is-gold should not affect native and crosssdk recipes Khem Raj
2014-02-17 19:34 ` [PATCH 6/6] uclibc: Update to git tip Khem Raj
2014-02-18 0:38 ` [PATCH 0/6] eglibc upgrade 2.19, uclibc upgrade and fixes Khem Raj
2014-02-18 8:17 ` Iorga, Cristian
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=20140218083708.GQ10078@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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