From: akuster808 <akuster808@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Armin Kuster <akuster@mvista.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] ldsoconf: allow extension via local.conf
Date: Wed, 11 Nov 2015 11:22:41 -0800 [thread overview]
Message-ID: <56439581.60906@gmail.com> (raw)
In-Reply-To: <CAMKF1srWCBeKpNEEDS2s3MxTYGvoH1iJdiQGj0L5rg6Y49LedQ@mail.gmail.com>
On 11/11/2015 10:39 AM, Khem Raj wrote:
> On Wed, Nov 11, 2015 at 9:41 AM, Armin Kuster <akuster808@gmail.com> wrote:
>> From: Armin Kuster <akuster@mvista.com>
>>
>> this allows extending ldconfig search path from local.conf
>>
>> Signed-off-by: Armin Kuster <akuster@mvista.com>
>> ---
>> meta/classes/image-ldconfig.bbclass | 6 ++++++
>> meta/conf/bitbake.conf | 3 +++
>> 2 files changed, 9 insertions(+)
>>
>> diff --git a/meta/classes/image-ldconfig.bbclass b/meta/classes/image-ldconfig.bbclass
>> index e9946da..ce10673 100644
>> --- a/meta/classes/image-ldconfig.bbclass
>> +++ b/meta/classes/image-ldconfig.bbclass
>> @@ -11,6 +11,12 @@ ld_so_conf() {
>>
>> rm -f ${STAGING_DIR_NATIVE}${sysconfdir_native}/ld.so.conf
>>
>> + # dump addition lib possible defined in local.conf
>> + for file in ${LDSOCONF};
>> + do
>> + echo ${file} >> ${STAGING_LDSO_CONF_DIR}/ld.so.conf
>> + done
>> +
>> # save lib dirs as defined in recipes
>> for file in `find ${STAGING_LDSO_CONF_DIR}/*/* -name "ld.so.conf"`;
>> do
>> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
>> index f0471f4..1f78c49 100644
>> --- a/meta/conf/bitbake.conf
>> +++ b/meta/conf/bitbake.conf
>> @@ -815,4 +815,7 @@ MULTILIB_VARIANTS ??= ""
>> #
>> # ldconfig stuff
>> #
>> +EXTRA_LDSOCONF ??= ""
>> +LDSOCONF = "/lib /lib64 /usr/lib /usr/lib64"
>
> is this going to exist always even when multilib is disbled ?
A sane default make more sense.
These libs are currently hardcoded in ldconfig-native.
#define LIBDIR "/usr/lib"
#define LIBDIR32 "/usr/lib32"
#define LIBDIR64 "/usr/lib64"
#define SLIBDIR "/lib"
#define SLIBDIR32 "/lib32"
#define SLIBDIR64 "/lib64"
looks like I missed lib32 versions.
> how about mips n32/o32/n64 all being in same rootfs
not checked today either. Maybe we can use this scheme to dynamically
append ldconfig search patches for the mips example?
ldconfig just gives a warning if the lib dirs don't not exist.
sounds like this needs to be extended to handle multi lib better or in a
saner method.
thanks,
- armin
>
>> +LSSOCONF += "${EXTRA_LDSOCONF}"
>> STAGING_LDSO_CONF_DIR = "${TMPDIR}/work-shared/ldconfig"
>> --
>> 2.3.5
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2015-11-11 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 17:41 [PATCH 0/2] Add ldconfig alt lib search paths Armin Kuster
2015-11-11 17:41 ` [PATCH 1/2] ldconfig: add method to extend ldconfig search dirs Armin Kuster
2015-12-08 16:33 ` akuster808
2015-12-08 17:51 ` Phil Blundell
[not found] ` <56674604.3030900@mvista.com>
2015-12-08 22:34 ` Phil Blundell
[not found] ` <566891A3.4040300@mvista.com>
2015-12-09 21:41 ` Phil Blundell
2015-11-11 17:41 ` [PATCH 2/2] ldsoconf: allow extension via local.conf Armin Kuster
2015-11-11 18:39 ` Khem Raj
2015-11-11 19:22 ` akuster808 [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=56439581.60906@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.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