* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (17 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (16 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (15 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (2 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (14 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (3 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (13 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (4 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (12 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (5 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (11 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (6 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (10 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (7 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (9 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (8 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (8 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (9 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (7 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (10 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (6 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (11 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (5 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (12 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (4 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (13 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (3 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (14 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
` (2 subsequent siblings)
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (15 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (16 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
2020-11-19 14:44 ` NIKHIL PATIL
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2930 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread
* Re: [yocto] Enaable to add binary in /usr/bin using .bb file
[not found] ` <1648EA3F963FB36F.4882@lists.yoctoproject.org>
` (17 preceding siblings ...)
2020-11-19 14:44 ` NIKHIL PATIL
@ 2020-11-19 14:44 ` NIKHIL PATIL
18 siblings, 0 replies; 31+ messages in thread
From: NIKHIL PATIL @ 2020-11-19 14:44 UTC (permalink / raw)
To: Nikhil Patil; +Cc: Quentin Schulz, Yocto-mailing-list
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
Hi ,
for these issue we got solution ,
obexpushd binary interpreter is on /lib64 folder , but in our
custom image /lib64 support is not there .
so we are trying to add lib64 support for our custom image .
For sato image by default it is taking lib64 support , so it work there.
On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org
<nikhilvp29=gmail.com@lists.yoctoproject.org> wrote:
> Hi ,
> Thank You very much , we are able to copy obexpushd to /usr/bin using
> .bb file.
>
> I have one more dout ;
> 1) We created our own custom image (*bitbake core-image-xxxx*) , after
> flashing image to board . when we run *obexpushd binary *it shows as
> follows :-
>
> root@intel-corei7-64:~#
> root@intel-corei7-64:~# obexpushd
> -sh: /usr/bin/obexpushd: No such file or directory
> root@intel-corei7-64:~# cd /usr/bin
> root@intel-corei7-64:/usr/bin# ls | grep obexpush
> obexpushd
> root@intel-corei7-64:/usr/bin#
>
> Even though binary is there it shows no such file or directory.
>
> 2) But when we are flashing a sato image (*bitbake* *core-image-sato-sdk *)
> , that time *obexpushd* binary is working fine .
>
> Why it is happening like these ?
> Is there any permission related issue with custom image and sato image
> ?
>
>
> On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <
> quentin.schulz@streamunlimited.com> wrote:
>
>> Hi,
>>
>> On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:
>> > Hi ,
>> > Yours correct only , but the thing is we are taking*
>> binary(obexpushd)*
>> > from other source and only need to copy that binary into* /usr/bin* of
>> our
>> > platform(*intel board*).
>> >
>> > Hence how we can achieve these using .bb file ? is there any sample
>> > example .
>> >
>>
>> I gave you what you have to do in the previous mail. Remove the last two
>> lines of your bb file.
>>
>> If it does not work, give the full error logs and what you're trying to
>> achieve and what you have.
>>
>> Quentin
>>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2986 bytes --]
^ permalink raw reply [flat|nested] 31+ messages in thread