From: Jack Mitchell <ml@communistcode.co.uk>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCHv5] libsoc: new recipe
Date: Sat, 14 Sep 2013 09:37:33 +0100 [thread overview]
Message-ID: <5234204D.9050904@communistcode.co.uk> (raw)
In-Reply-To: <CAP9ODKrVsBfpHDtwp031feCOitJEG6fi=bKah4e0sH5_Wkh6cg@mail.gmail.com>
On 09/13/13 23:22, Otavio Salvador wrote:
> On Fri, Sep 13, 2013 at 7:15 PM, Jack Mitchell <ml@communistcode.co.uk> wrote:
>> From: Jack Mitchell <jack@embed.me.uk>
>>
>> Signed-off-by: Jack Mitchell <jack@embed.me.uk>
> ...
>
> The recipe is clean now ... but ...
>
>> --- /dev/null
>> +++ b/meta-oe/recipes-support/libsoc/libsoc_0.3.bb
>> @@ -0,0 +1,14 @@
>> +SUMMARY = "libsoc is a C library for interfacing with common SoC peripherals through generic kernel interfaces"
>> +HOMEPAGE = "https://github.com/jackmitch/libsoc"
>> +
>> +LICENSE = "LGPLv2.1"
>> +LIC_FILES_CHKSUM = "file://COPYING;md5=e0bfebea12a718922225ba987b2126a5"
>> +
>> +inherit autotools
>> +
>> +SRCREV = "0764ee52b590d5ccb4bd4698f0011496b536ed70"
>> +SRC_URI = "git://github.com/jackmitch/libsoc.git"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +RDEPENDS_${PN} = "libgcc"
> I am a little concerned /why/ this is need. Your code seems quite
> simple and I don't understand why this special need. Did you try to
> install and use it without this RDEPENDS ? It should work just fine.
>
There seems to be a bug with the eglibc recipe as noted in a previous
discussion [1] where pthreads requires libgcc.so to be available but it
isn't pulled in as a requirement. Now, I believe this goes largly
unnoticed as there are very few functions which actually require the
libgcc.so lib, but it happens that one of the functions I use
(pthread_cancel), does require it, so I run into this bug and as such
have to depened on RDEPENDS = "libgcc" in order to ensure it is in the
rootfs.
In the next version of the library I think I am going to see if I can
work round using pthread_cancel in favour of a less awkward function.
Cheers,
Jack.
[1] http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/37086
next prev parent reply other threads:[~2013-09-14 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 22:15 [meta-oe][PATCHv5] libsoc: new recipe Jack Mitchell
2013-09-13 22:22 ` Otavio Salvador
2013-09-14 8:37 ` Jack Mitchell [this message]
2013-09-14 14:15 ` Otavio Salvador
2013-09-19 8:39 ` Jack Mitchell
2013-09-19 12:11 ` Martin Jansa
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=5234204D.9050904@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.