All of lore.kernel.org
 help / color / mirror / Atom feed
* libmcrypt not part of the image
@ 2015-08-07  9:25 yocto yocto
  2015-08-07 10:04 ` Paul Eggleton
  2015-08-08 19:43 ` Khem Raj
  0 siblings, 2 replies; 3+ messages in thread
From: yocto yocto @ 2015-08-07  9:25 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 618 bytes --]

I added the meta-openembedded layer to my configuration. I want to have
libmcrypt (in meta-openembedded/meta-oe/recipes-support) on my system:

IMAGE_INSTALL += "libmcrypt"

The library (libmcrypt.so) is actually being built. Everything is located
in "libmcrypt/2.5.8-r0/package/usr", however after flashing the image
libmcrypt is not part of the filesystem.

I tried writing some kind of "libmcrypt_%.bbappend" with

do_install() {
install -m 0755 ${WORKDIR}/package/usr ${D}/
}

However, I get a bitbake error that do_install failed but there is exact
message. Any ideas how to solve this properly?

[-- Attachment #2: Type: text/html, Size: 899 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libmcrypt not part of the image
  2015-08-07  9:25 libmcrypt not part of the image yocto yocto
@ 2015-08-07 10:04 ` Paul Eggleton
  2015-08-08 19:43 ` Khem Raj
  1 sibling, 0 replies; 3+ messages in thread
From: Paul Eggleton @ 2015-08-07 10:04 UTC (permalink / raw)
  To: yocto yocto; +Cc: yocto

On Friday 07 August 2015 11:25:40 yocto yocto wrote:
> I added the meta-openembedded layer to my configuration. I want to have
> libmcrypt (in meta-openembedded/meta-oe/recipes-support) on my system:
> 
> IMAGE_INSTALL += "libmcrypt"

Where did you add this exactly?

> The library (libmcrypt.so) is actually being built. Everything is located
> in "libmcrypt/2.5.8-r0/package/usr", however after flashing the image
> libmcrypt is not part of the filesystem.
> 
> I tried writing some kind of "libmcrypt_%.bbappend" with
> 
> do_install() {
> install -m 0755 ${WORKDIR}/package/usr ${D}/
> }
> 
> However, I get a bitbake error that do_install failed but there is exact
> message. Any ideas how to solve this properly?

If the files are under package/ then do_install is already working fine, so your 
hack definitely isn't going to help.

When I have problems like this I generally follow this procedure to find the 
issue:

1) Is do_install working? (check "image" subdirectory under the workdir for 
the recipe, which is ${D})

2) Has do_package put the file in the package you think it should be in? (look 
in "packages-split" under the workdir for the recipe; there are subdirectories 
for each package created by the recipe)

3) Is the package really being installed? (check bitbake -e imagename and look 
at the IMAGE_INSTALL value to see if it's really in there, and also look at 
log.do_rootfs for the image - is the package mentioned?)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libmcrypt not part of the image
  2015-08-07  9:25 libmcrypt not part of the image yocto yocto
  2015-08-07 10:04 ` Paul Eggleton
@ 2015-08-08 19:43 ` Khem Raj
  1 sibling, 0 replies; 3+ messages in thread
From: Khem Raj @ 2015-08-08 19:43 UTC (permalink / raw)
  To: yocto yocto; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]


> On Aug 7, 2015, at 2:25 AM, yocto yocto <yoctomailinglist@gmail.com> wrote:
> 
> I added the meta-openembedded layer to my configuration. I want to have libmcrypt (in meta-openembedded/meta-oe/recipes-support) on my system:
> 
> IMAGE_INSTALL += "libmcrypt"
> 
> The library (libmcrypt.so) is actually being built. Everything is located in "libmcrypt/2.5.8-r0/package/usr", however after flashing the image libmcrypt is not part of the filesystem.
> 

build system has preset rules for shared libraries that follow the versioning scheme, in that scheme foo.so is a symlink to real shared object which is something like foo.x.y.z or something like that. then packager goes in and bundles the .so into -dev ipk and real shared object into proper ipk and all works. So is this library using versioning ? if not you have to jump through some hoops to let system know about that so it stats treating .so as final shared object and not as symlink.


> I tried writing some kind of "libmcrypt_%.bbappend" with
> 
> do_install() {
> 	install -m 0755 ${WORKDIR}/package/usr ${D}/
> }

you need to specify filenames or wildchars something like  ${WORKDIR}/package/usr/bin/mybinary or something like that look at manpage of install utility for more insights

> 
> However, I get a bitbake error that do_install failed but there is exact message. Any ideas how to solve this properly?
> 
> 
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-08-08 19:43 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-07  9:25 libmcrypt not part of the image yocto yocto
2015-08-07 10:04 ` Paul Eggleton
2015-08-08 19:43 ` Khem Raj

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.