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