From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: LSB support?
Date: Fri, 16 Mar 2012 10:36:52 -0500 [thread overview]
Message-ID: <4F635E14.7000707@windriver.com> (raw)
In-Reply-To: <1331875115.1041.67.camel@localhost.localdomain>
On 3/16/12 12:18 AM, Ni Qingliang wrote:
> when building qemux86-64 arch core-image-lsb (distro is poky-lsb), I got
> /usr/lib/../lib/libXrandr.so.2: undefined reference to
> `memcpy@GLIBC_2.14' when 'do_compile' gconf 3.2.3.
>
> the default eglibc is 2.13, why it needs 2.14?
Without anything further, the only guess I can make is that either you aren't
using the version of glibc you think you are, it's gotten some host
contamination, an explicit reference was added to libXrandr (doubtful), or you
are using something that was built/cached from a previous build. (i.e. did you
build w/ eglibc 2.14/2.15 -- and then switch back to eglibc 2.13 for some reason?)
On 3/15/12 9:38 PM, Ni Qingliang wrote:
> first, thanks your reply.
>
> Because I can't use task-core-lsb on my device (flash space is not
> enough), I have to make a custom lsb-base image (without
> perl/python/graphics).
>
> I have checked the "linuxstdbase", and it will change the configure
> option of some packages.
>
> Indeed, I think the daemon/failure/warning fuctions should be considered
> in package lsb's RDEPENDS.
>
> what I want to know is the rdepends or where is the
> daemon/failure/warning.
It certainly looks like a component is missing somewhere in the shell scrips
that are provided by the LSB functions. I would assume that the
depends/provides is setup properly to point to whatever should be providing the
missing daemon, failure, warning commands. If it's not (or if by default -- non
lsb mode) they're not being built, it's a definite bug. You shouldn't be able
to build a non-functional systems.
Please file a defect on bugzilla.yoctoproject.org. I will attempt to
investigate it (or someone else can). Hopefully it's just as a simple as a
missing dependency.
--Mark
> On Fri, 2012-03-16 at 00:25 +0800, Mark Hatle wrote:
>> On 3/15/12 3:18 AM, Ni Qingliang wrote:
>>> Hello, I'm working on custom lsb-base image using oe-core.
>>>
>>> and when using the lsb script, found error:
>>>
>>> lsb_start_daemon line 44: daemon command not found.
>>>
>>> similar thing happend on lsb_log_message: failure and warning command
>>> not found.
>>>
>>> maybe these function should be defined in /etc/init.d/functions?
>>>
>>> but there are not these function in this file (belongs to initscripts).
>>
>> Did you enable the LSB distribution settings? Without this, various components
>> may not be available.
>>
>> In Poky, there is a "poky-lsb" distribution type:
>>
>> DISTRO = "poky-lsb"
>> DISTROOVERRIDES = "poky:linuxstdbase"
>>
>> DISTRO_FEATURES_append = " pam largefile opengl"
>> PREFERRED_PROVIDER_virtual/libx11 = "libx11"
>>
>> (as well as using the core-image-lsb and/or task-core-lsb components.)
>>
>> If you've tried this and those items are still broken, let me know and I can
>> help investigate further. (One final note, only LSB 1.4 is currently supported.)
>>
>> --Mark
>>
>>> Any idea?
>>>
>>> thanks!
>>>
>>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-03-16 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 8:18 LSB support? Ni Qingliang
2012-03-15 16:25 ` Mark Hatle
2012-03-16 2:38 ` Ni Qingliang
2012-03-16 5:18 ` Ni Qingliang
2012-03-16 15:36 ` Mark Hatle [this message]
2012-03-19 1:47 ` Ni Qingliang
2012-03-19 6:33 ` Ni Qingliang
2012-03-19 16:07 ` Mark Hatle
2012-03-20 2:56 ` Ni Qingliang
2012-03-20 9:20 ` Ni Qingliang
2012-03-21 8:45 ` gconf build error Ni Qingliang
2012-03-23 8:32 ` Ni Qingliang
2012-03-23 9:30 ` Richard Purdie
2012-03-23 9:40 ` Ni Qingliang
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=4F635E14.7000707@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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