Poky Project Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: "poky@pokylinux.org" <poky@pokylinux.org>
Subject: Re: [PULL] fixes to eglibc and busybox
Date: Thu, 04 Nov 2010 14:17:46 -0700	[thread overview]
Message-ID: <4CD322FA.3030505@intel.com> (raw)
In-Reply-To: <4CD2F9B1.3040903@windriver.com>

On 11/04/2010 11:21 AM, Mark Hatle wrote:
> On 11/4/10 1:10 PM, Saul Wold wrote:
>> On 11/04/2010 08:13 AM, Mark Hatle wrote:
>>> On 11/3/10 7:55 PM, Cui, Dexuan wrote:
>>>> BTW: The fix to busybox is a RESEND since looks it was neglected. :-)
>>>>
>>>> $ scripts/create-pull-request -r 2ecf311fbca970f6ea2d80accc3f925b097b664e -b dcui/master
>>>> Note:<commit_id>     parameter assumed as 'HEAD'
>>>>
>>>>      meta/recipes-core/busybox/busybox-1.16.2/defconfig |   14 +++++++-------
>>>>      meta/recipes-core/eglibc/eglibc-package.inc        |    2 +-
>>>>      meta/recipes-core/eglibc/eglibc_2.12.bb            |    2 +-
>>>>      3 files changed, 9 insertions(+), 9 deletions(-)
>>>>
>>>> Dexuan Cui (2):
>>>>           busybox: enable more options for tar to support more file formats.
>>>>           eglibc: install the missing /etc/ld.so.conf into target
>>>>
>>>> Pull URL: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dcui/master
>>>>
>>>>
>>>> commit 61e77cb2e9a240110c50925d1b3f908d14b02f24
>>>> Author: Dexuan Cui<dexuan.cui@intel.com>
>>>> Date:   Tue Nov 2 15:42:09 2010 +0800
>>>>
>>>>         eglibc: install the missing /etc/ld.so.conf into target
>>>
>>> My preference is that /etc/ld.so.conf not always be installed onto the target.
>>> It's not required for anything to function, and as long as only default library
>>> directories are used, even ldconfig will run properly with it not existing (or
>>> empty).
>>>
>>> If we do install it, we need to make sure it's empty.  I don't think it's
>>> appropriate to advocate alternative library directories on an embedded platform.
>>>
>> Mark,
>>
>> The default one that we are installing contains entries for
>> /usr/local/lib and /usr/X11R6/lib
>>
>> I understand you would rather it be empty, is that correct?
>
> Generally speaking, we should not be placing software into /usr/local/lib as
> part of the Yocto work.  That location, and /opt/* are reserved for system
> administrators to place their own software...  So that location, if necessary,
> should be done by the system admin.
>
Agreed

> The /usr/X11R6/lib location should be a symlink to /usr/lib.  As all of the X
> libraries are installed into /usr/lib... so there is no reason to have this
> location in the ld.so.conf.  (Note I have not verified that that is a symlink...
> or if the directory is empty -- but it should be...)
>
I don't think we even install an X11R6 directory anymore, so it can be 
removed!  CONFIRMED no /usr/X11R6 dir in a yocto image.

Sau!

> So yes, my preference is that it's either absent or empty for embedded systems.
>
> --Mark
>
>>
>> Sau!
>>
>>
>>>>         ${sysconfdir} should be added into FILES_${PN}.
>>>>
>>>>         Fixes [BUGID #511]
>>>>
>>>>         Signed-off-by: Dexuan Cui<dexuan.cui@intel.com>
>>>>
>>>> commit b952fae48c45e39a14ec9c24b0ee544a741c3f69
>>>> Author: Dexuan Cui<dexuan.cui@intel.com>
>>>> Date:   Tue Oct 26 15:10:26 2010 +0800
>>>>
>>>>         busybox: enable more options for tar to support more file formats.
>>>>
>>>>         Fixes [BUGID #495]
>>>>
>>>>         Signed-off-by: Dexuan Cui<dexuan.cui@intel.com>
>>>> _______________________________________________
>>>> poky mailing list
>>>> poky@pokylinux.org
>>>> https://lists.pokylinux.org/listinfo/poky
>>>
>>> _______________________________________________
>>> poky mailing list
>>> poky@pokylinux.org
>>> https://lists.pokylinux.org/listinfo/poky
>>>
>>
>> _______________________________________________
>> poky mailing list
>> poky@pokylinux.org
>> https://lists.pokylinux.org/listinfo/poky
>
> _______________________________________________
> poky mailing list
> poky@pokylinux.org
> https://lists.pokylinux.org/listinfo/poky
>



  reply	other threads:[~2010-11-04 21:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20  8:56 [PULL] fixes for bash and nfs-utils Qing He
2010-10-20  9:28 ` Richard Purdie
2010-10-22  0:54 ` [PULL] libtheora: add DEPENDS on libogg Cui, Dexuan
2010-10-22  9:24   ` Richard Purdie
2010-10-26  7:24   ` [PULL] busybox: enable more options for tar to support more file formats Cui, Dexuan
2010-11-04  0:55     ` [PULL] fixes to eglibc and busybox Cui, Dexuan
2010-11-04 15:13       ` Mark Hatle
2010-11-04 18:10         ` Saul Wold
2010-11-04 18:21           ` Mark Hatle
2010-11-04 21:17             ` Saul Wold [this message]
2010-11-05  0:29               ` Cui, Dexuan

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=4CD322FA.3030505@intel.com \
    --to=saul.wold@intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=poky@pokylinux.org \
    /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