I had a similar problem where the rapidjson recipe was not working only on sumo.
The problem was that the default ${PN} package was empty so it would
not be generated, but do_rootfs would try to include it.
It helped to add a bbappend with the following line:
FILES_${PN} = " ${includedir}/ "
in
I created a custom meta-layer to build libfmt 4.1.0 (
https://github.com/fmtlib/fmt).
Since this library uses cmake, I created this receipe:
*SUMMARY = "fmt"*
*SECTION = "base"*
*SRC_URI = "https://github.com/fmtlib/fmt/archive/${PV}.tar.gz
Hi,
To give you more detail,I am trying to add gstreamer-1.0 support in
framework which is already having gstreamer-0.10.
Now gstreamer binaries are built in Intel 80386 32 bit format,while my
machine is amd,64 bit.So what i am doing i am configuring
and compiling the gstreamer plugin packages
On 2015-09-23 06:13, Mayank Agarwal wrote:
Hi,
To give you more detail,I am trying to add gstreamer-1.0 support in framework
which is already having gstreamer-0.10.
Now gstreamer binaries are built in Intel 80386 32 bit format,while my machine
is amd,64 bit.So what i am doing i am
bitbake -u depexp -g name segfault because of not gui environment
you can get dpendency dot file using bitbake image-name -g. not bitbake bash -g
I think that the problem is do_rootfs error cause is busybox
when you create rootfs, it is stranged to create a bash link not /bin/sh
>> Error:
> On Sep 22, 2015, at 12:08 AM, Mayank Agarwal
> wrote:
>
> Hi
>
> While installing gstreamer-1.0 i am facing following errors in do_rootfs:
>
> Configuring xfsprogs-mkfs.
> Configuring packagegroup-rdk-oss-mediaserver.
> Configuring gst-plugins-bad-linsys.
>
Hi
While installing gstreamer-1.0 i am facing following errors in do_rootfs:
Configuring xfsprogs-mkfs.
Configuring packagegroup-rdk-oss-mediaserver.
Configuring gst-plugins-bad-linsys.
Configuring gst-plugins-good-isomp4.
Collected errors:
* opkg_install_cmd: Cannot install package
Seg fault? Thats really weird,
Please specify your target system, host system, yocto release. This stuff
shoudn't segfault at all, something would be really messy on your build
environment.
Did you tried this: https://github.com/dv1/meta-gstreamer1.0 ?
It seems to be what you're looking for :)
binaries are there in qemux/usr/lib/gstreamer-1.0 but they are not getting
installed in final image.
is this empty by any chance:
i didn't get you.
Regards
Mayank
On Tue, Sep 22, 2015 at 12:42 PM, Khem Raj wrote:
>
> > On Sep 22, 2015, at 12:08 AM, Mayank Agarwal <
>
Hi,
I am getting the below error in do_rootfs:
ERROR: Unable to install packages. Command
returned 255:
I uderstand this error comes from certificate validation
failure.
Is there any option i can override the certificate validation
in do_rootfs and get the binaries imstalled in final image
This will depend on what is selecting it to your image...
Taking a look on bash dependecies here (I'm in Daisy) it has nothing that
depend on bash. So, the right question is, "Why bitbake is trying to
install it?". I suggest you to run `bitbake -u depexp -g bash' and see at
"Reverse
2015-09-22
This will depend on what is selecting it to your image...
Taking a look on bash dependecies here (I'm in Daisy) it has nothing that
depend on bash. So, the right question is, "Why bitbake is trying to
install it?". I suggest you to run `bitbake -u depexp -g bash' and see at
"Reverse Depends" if
On 2015-09-22 08:53, Mayank Agarwal wrote:
Thanks Daniel for your help.Please specify how can i remove it
It would be a lot easier to help you diagnose your problem if you provide
more data:
* What version of Yocto are you using?
* What is your target machine?
* What image are you trying
>From that error:
Error: not linking /1.0-r0/rootfs//bin/bash to /bin/busybox.nosuid since
rootfs//bin/bash exists and is not a link
Any solutions for above,even if i create symlink this error doesn't go
Regards
Mayank
On Tue, Sep 22, 2015 at 7:47 PM, Daniel. wrote:
>
Will you use bash? If not, try to remove it from image, so /bin/bash isn't
created.
Cheers,
- dhs
2015-09-22 11:42 GMT-03:00 Mayank Agarwal :
> From that error:
> Error: not linking /1.0-r0/rootfs//bin/bash to /bin/busybox.nosuid since
> rootfs//bin/bash exists and
Thanks Daniel for your help.Please specify how can i remove it
Regards
Mayank
On Tue, Sep 22, 2015 at 8:21 PM, Daniel. wrote:
> Will you use bash? If not, try to remove it from image, so /bin/bash isn't
> created.
>
>
> Cheers,
> - dhs
>
> 2015-09-22 11:42 GMT-03:00
16 matches
Mail list logo