From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCHv2] libsoc: new recipe
Date: Fri, 13 Sep 2013 16:17:51 +0100 [thread overview]
Message-ID: <52332C9F.50904@communistcode.co.uk> (raw)
In-Reply-To: <l0v937$88j$1@ger.gmane.org>
On 13/09/13 15:56, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 13-09-13 16:53, Paul Eggleton schreef:
>> On Friday 13 September 2013 15:23:36 Jack Mitchell wrote:
>>> On 13/09/13 15:18, Koen Kooi wrote:
>>>> Op 13-09-13 15:22, Jack Mitchell schreef:
>>>>> From: Jack Mitchell <jack@embed.me.uk>
>>>>>
>>>>> Signed-off-by: Jack Mitchell <jack@embed.me.uk> ---
>>>>>
>>>>> Change from v1: added signed-off-by
>>>>>
>>>>> meta-oe/recipes-support/libsoc/libsoc_0.3.bb | 18
>>>>> ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode
>>>>> 100644 meta-oe/recipes-support/libsoc/libsoc_0.3.bb
>>>>>
>>>>> diff --git a/meta-oe/recipes-support/libsoc/libsoc_0.3.bb
>>>>> b/meta-oe/recipes-support/libsoc/libsoc_0.3.bb new file mode 100644
>>>>> index 0000000..e91e152 --- /dev/null +++
>>>>> b/meta-oe/recipes-support/libsoc/libsoc_0.3.bb @@ -0,0 +1,18 @@
>>>>> +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 + +DEPENDS = "libgcc"
>>>>
>>>> Isn't that automatically implied with gcc-cross?
>>>
>>> I wasn't sure, so I thought I would stick it in and see if anyone
>>> piped up, I'll remove it in v3.
>>>
>>> Also on that note I noticed that Apache2 also DEPENDS on libgcc, is
>>> that also wrong?
>>
>> I don't know anything about this particular recipe, but IIRC, apache
>> complains if libgcc is not installed at runtime, and at least when I
>> added that to the recipe it was not being installed otherwise.
>
> But that's RDEPENDS, no?
>
> regards,
>
> Koen
My apologies, I just checked and it is as an RDEPENDS. The reason that I
put libgcc in the DEPENDS is that when I was developing libsoc I ran
into a function (pthread_cancel) which required libgcc.so.1 to be on the
rootfs, which it wasn't. Having just checked a new build now, with only
core-image-minimal there doesn't appear to be any libgcc.so.1 in the
rootfs again, so should I have libgcc in RDEPENDS? I thought OE put all
the libraries it linked against in the rootfs automatically... or have I
misunderstood?
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambrideshire, UK
http://www.embed.me.uk
--
next prev parent reply other threads:[~2013-09-13 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 13:22 [meta-oe][PATCHv2] libsoc: new recipe Jack Mitchell
2013-09-13 14:18 ` Koen Kooi
2013-09-13 14:23 ` Jack Mitchell
2013-09-13 14:53 ` Paul Eggleton
2013-09-13 14:56 ` Koen Kooi
2013-09-13 15:17 ` Jack Mitchell [this message]
2013-09-13 15:46 ` Jack Mitchell
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=52332C9F.50904@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@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