error in do_rootfs

error in do_rootfs

[Mayank Agarwal]

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

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

Regards
Mayank

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

Re: error in do_rootfs

[Daniel.]

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

There should be a log.do_rootfs in something like
BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
a proper failure message with the command that triggered the failure and is
output.

Cheers,
- dhs

2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:

> 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
>
> Regards
> Mayank
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
*"Do or do not. There is no try"*
  *Yoda Master*

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

Re: error in do_rootfs

[Mayank Agarwal]

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

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. <danielhilst@gmail.com> wrote:

> There should be a log.do_rootfs in something like
> BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
> a proper failure message with the command that triggered the failure and is
> output.
>
> Cheers,
> - dhs
>
> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:
>
>> 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
>>
>> Regards
>> Mayank
>>
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
>
> --
> *"Do or do not. There is no try"*
>   *Yoda Master*
>

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

Re: error in do_rootfs

[Daniel.]

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

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 <mayank77fromindia@gmail.com>:

> 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. <danielhilst@gmail.com> wrote:
>
>> There should be a log.do_rootfs in something like
>> BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
>> a proper failure message with the command that triggered the failure and is
>> output.
>>
>> Cheers,
>> - dhs
>>
>> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:
>>
>>> 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
>>>
>>> Regards
>>> Mayank
>>>
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>
>>
>> --
>> *"Do or do not. There is no try"*
>>   *Yoda Master*
>>
>
>


-- 
*"Do or do not. There is no try"*
  *Yoda Master*

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

Re: error in do_rootfs

[Mayank Agarwal]

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

Thanks Daniel for your help.Please specify how can i remove it

Regards
Mayank

On Tue, Sep 22, 2015 at 8:21 PM, Daniel. <danielhilst@gmail.com> 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 <mayank77fromindia@gmail.com>:
>
>> 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. <danielhilst@gmail.com> wrote:
>>
>>> There should be a log.do_rootfs in something like
>>> BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
>>> a proper failure message with the command that triggered the failure and is
>>> output.
>>>
>>> Cheers,
>>> - dhs
>>>
>>> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:
>>>
>>>> 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
>>>>
>>>> Regards
>>>> Mayank
>>>>
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>>
>>>
>>>
>>> --
>>> *"Do or do not. There is no try"*
>>>   *Yoda Master*
>>>
>>
>>
>
>
> --
> *"Do or do not. There is no try"*
>   *Yoda Master*
>

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

Re: error in do_rootfs

[Daniel.]

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

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 11:53 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:

> Thanks Daniel for your help.Please specify how can i remove it
>
> Regards
> Mayank
>
> On Tue, Sep 22, 2015 at 8:21 PM, Daniel. <danielhilst@gmail.com> 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 <mayank77fromindia@gmail.com>:
>>
>>> 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. <danielhilst@gmail.com> wrote:
>>>
>>>> There should be a log.do_rootfs in something like
>>>> BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
>>>> a proper failure message with the command that triggered the failure and is
>>>> output.
>>>>
>>>> Cheers,
>>>> - dhs
>>>>
>>>> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:
>>>>
>>>>> 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
>>>>>
>>>>> Regards
>>>>> Mayank
>>>>>
>>>>>
>>>>> --
>>>>> _______________________________________________
>>>>> yocto mailing list
>>>>> yocto@yoctoproject.org
>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *"Do or do not. There is no try"*
>>>>   *Yoda Master*
>>>>
>>>
>>>
>>
>>
>> --
>> *"Do or do not. There is no try"*
>>   *Yoda Master*
>>
>
>


-- 
*"Do or do not. There is no try"*
  *Yoda Master*

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

Re: error in do_rootfs

[Daniel.]

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

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 there is something selecting bash. Also take a look at
DISTRO_FEATURES and IMAGE_FEATURES, did you mess with them?

Cheers,


2015-09-22 12:04 GMT-03:00 Daniel. <danielhilst@gmail.com>:

> 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 11:53 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:
>
>> Thanks Daniel for your help.Please specify how can i remove it
>>
>> Regards
>> Mayank
>>
>> On Tue, Sep 22, 2015 at 8:21 PM, Daniel. <danielhilst@gmail.com> 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 <mayank77fromindia@gmail.com>:
>>>
>>>> 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. <danielhilst@gmail.com> wrote:
>>>>
>>>>> There should be a log.do_rootfs in something like
>>>>> BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
>>>>> a proper failure message with the command that triggered the failure and is
>>>>> output.
>>>>>
>>>>> Cheers,
>>>>> - dhs
>>>>>
>>>>> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>
>>>>> :
>>>>>
>>>>>> 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
>>>>>>
>>>>>> Regards
>>>>>> Mayank
>>>>>>
>>>>>>
>>>>>> --
>>>>>> _______________________________________________
>>>>>> yocto mailing list
>>>>>> yocto@yoctoproject.org
>>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *"Do or do not. There is no try"*
>>>>>   *Yoda Master*
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *"Do or do not. There is no try"*
>>>   *Yoda Master*
>>>
>>
>>
>
>
> --
> *"Do or do not. There is no try"*
>   *Yoda Master*
>



-- 
*"Do or do not. There is no try"*
  *Yoda Master*

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

Re: error in do_rootfs

[Daniel.]

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

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 :)

Cheers,
- dhs

2015-09-22 12:35 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:

> 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 ubuntu and copy the whole
> source from there,after that i am doing do_install
> in my recipe.In my recipe i have set noexec=1 for
> do_fetch,do_configure,do_compile.It is able to install binaries in
> image/usr/lib and sysroot folder according to what i write in do_install
> but in installing the binaries to final image it is giving these errors:
>
> i hope what i am doing above is right.
> on doing bitbake -u depexp -g bash i am seg fault: error
>
> Regards
> Mayank
>
>
>
>
>
>
>
> On Tue, Sep 22, 2015 at 8:37 PM, Daniel. <danielhilst@gmail.com> wrote:
>
>> 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 there is something selecting bash. Also take a look at
>> DISTRO_FEATURES and IMAGE_FEATURES, did you mess with them?
>>
>> Cheers,
>>
>>
>> 2015-09-22 12:04 GMT-03:00 Daniel. <danielhilst@gmail.com>:
>>
>>> 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 11:53 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com>:
>>>
>>>> Thanks Daniel for your help.Please specify how can i remove it
>>>>
>>>> Regards
>>>> Mayank
>>>>
>>>> On Tue, Sep 22, 2015 at 8:21 PM, Daniel. <danielhilst@gmail.com> 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 <mayank77fromindia@gmail.com
>>>>> >:
>>>>>
>>>>>> 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. <danielhilst@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> There should be a log.do_rootfs in something like
>>>>>>> BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find
>>>>>>> a proper failure message with the command that triggered the failure and is
>>>>>>> output.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> - dhs
>>>>>>>
>>>>>>> 2015-09-22 6:36 GMT-03:00 Mayank Agarwal <
>>>>>>> mayank77fromindia@gmail.com>:
>>>>>>>
>>>>>>>> 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
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Mayank
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> _______________________________________________
>>>>>>>> yocto mailing list
>>>>>>>> yocto@yoctoproject.org
>>>>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *"Do or do not. There is no try"*
>>>>>>>   *Yoda Master*
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *"Do or do not. There is no try"*
>>>>>   *Yoda Master*
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *"Do or do not. There is no try"*
>>>   *Yoda Master*
>>>
>>
>>
>>
>> --
>> *"Do or do not. There is no try"*
>>   *Yoda Master*
>>
>
>


-- 
*"Do or do not. There is no try"*
  *Yoda Master*

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

Re: error in do_rootfs

[Gary Thomas]

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 to build?
   * What changes have you made to local.conf that might affect the result,
     e.g. adding any additional packages, etc?
More details, the better.

> On Tue, Sep 22, 2015 at 8:21 PM, Daniel. <danielhilst@gmail.com <mailto:danielhilst@gmail.com>> 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 <mayank77fromindia@gmail.com <mailto:mayank77fromindia@gmail.com>>:
>
>          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. <danielhilst@gmail.com <mailto:danielhilst@gmail.com>> wrote:
>
>             There should be a log.do_rootfs in something like BUILD_DIR/tmp/work/MACHINE-TOOLCHAIN/IMAGE/PV-PR/temp/. There you will find a proper failure message with the command
>             that triggered the failure and is output.
>
>             Cheers,
>             - dhs
>
>             2015-09-22 6:36 GMT-03:00 Mayank Agarwal <mayank77fromindia@gmail.com <mailto:mayank77fromindia@gmail.com>>:
>
>                 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
>
>                 Regards
>                 Mayank
>
>
>                 --
>                 _______________________________________________
>                 yocto mailing list
>                 yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>                 https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
>             --
>             /"Do or do not. There is no try"/
>             ///*Yoda Master*/
>
>
>
>
>
>     --
>     /"Do or do not. There is no try"/
>     ///*Yoda Master*/
>
>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Error in do_rootfs

[Mayank Agarwal]

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

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 ubuntu and copy the whole
source from there,after that i am doing do_install
in my recipe.In my recipe i have set noexec=1 for
do_fetch,do_configure,do_compile.It is able to install binaries in
image/usr/lib and sysroot folder according to what i write in do_install
but in installing the binaries to final image it is giving these errors:

i hope what i am doing above is right.

In log.do_rootfs file i am getting below error:

ERROR: Unable to install packages. Command  returned 255:


update-alternatives: Error: not linking /rootfs//bin/bash to
/bin/busybox.nosuid since rootfs//bin/bash exists and is not a link

What changes i should do in recipe file in order to overcome these errors.

Regards
Mayank

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

Re: Error in do_rootfs

[Gary Thomas]

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 configuring
> and compiling the gstreamer plugin packages on ubuntu and copy the whole source from there,after that i am doing do_install
> in my recipe.In my recipe i have set noexec=1 for do_fetch,do_configure,do_compile.It is able to install binaries in image/usr/lib and sysroot folder according to what i write in
> do_install but in installing the binaries to final image it is giving these errors:
>
> i hope what i am doing above is right.
>
> In log.do_rootfs file i am getting below error:
>
> ERROR: Unable to install packages. Command  returned 255:
>
>
> update-alternatives: Error: not linking /rootfs//bin/bash to /bin/busybox.nosuid since rootfs//bin/bash exists and is not a link
>
> What changes i should do in recipe file in order to overcome these errors.

Why are you trying to move binaries around (from your build host
directly into the target)?  You should be able to just add the
gstreamer-1.x recipes to your build and have it work.  Note there
is no problem with gstreamer-1.x being installed alongside the
older gstreamer-0.10

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: error in do_rootfs

[신택현 (Taek Hyun Shin)]

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

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: not linking /1.0-r0/rootfs//bin/bash to /bin/busybox.nosuid since

>> rootfs//bin/bash exists and is not a link

 

Also, if you use systemd, bash is installed because of the dependence of systemd.

 

Thanks

 

Best regards,

Wily Taekhyun Shin

 

=============================================================================
Wily Taekhyun Shin

Research Engineer
R&D Center
Telechips Inc.
Tel : + 82-2-3443-6792(Ext.390)

Fax : + 82-2-6424-7793 

Mobile : + 82-10-4376-5530

E-mail : thshin@telechips.com <blocked::blocked::blocked::blocked::blocked::blocked::blocked::blocked::blocked::blocked::mailto:ksjeon@telechips.com> 
=============================================================================



 


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

error in do_rootfs

[Mayank Agarwal]

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

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 gst-plugins-base-version.

ERROR: Function failed: do_rootfs




Regards
Mayank

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

Re: error in do_rootfs

[Khem Raj]

> On Sep 22, 2015, at 12:08 AM, Mayank Agarwal <mayank77fromindia@gmail.com> 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.
> Configuring gst-plugins-good-isomp4.
> Collected errors:
>  * opkg_install_cmd: Cannot install package gst-plugins-base-version.

is this empty by any chance ?

Re: error in do_rootfs

[Mayank Agarwal]

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

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 <raj.khem@gmail.com> wrote:

>
> > On Sep 22, 2015, at 12:08 AM, Mayank Agarwal <
> mayank77fromindia@gmail.com> 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.
> > Configuring gst-plugins-good-isomp4.
> > Collected errors:
> >  * opkg_install_cmd: Cannot install package gst-plugins-base-version.
>
> is this empty by any chance ?
>
>

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