All of lore.kernel.org
 help / color / mirror / Atom feed
* File not found when trying to run an executable not build by Yocto
@ 2014-02-03 15:51 David Welch
  2014-02-03 16:28 ` Christian Ege
  0 siblings, 1 reply; 4+ messages in thread
From: David Welch @ 2014-02-03 15:51 UTC (permalink / raw)
  To: yocto

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

Hi,

I am building an image for an embedded system using the chiefriver and
kernel 3.12.9.  I am using Ubuntu as our base system.

The image builds and boots fine which is great but we have some binaries
built on Ubuntu which must run on the Yocto image.  When we copy these
across and try and run them we get a "File Not Found" error.

Why would this be?  Doing file on our ubuntu executables we get:

/bin/true: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked (uses shared libs), for GNU/Linux 2.6.24,
BuildID[sha1]=0x2b45516be4a9f45b1127d54efb0d42e5f69b1c82, stripped

The Yocto executables are the same except instead of GNU/Linux 2.6.24 it is
2.6.16.  It that a problem?

Also, on ubuntu we are running libc-2.17 but on Yocto it is libc-2.18.  Is
that a problem?

Thanks for any assistance,
Dave

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

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

* Re: File not found when trying to run an executable not build by Yocto
  2014-02-03 15:51 File not found when trying to run an executable not build by Yocto David Welch
@ 2014-02-03 16:28 ` Christian Ege
  2014-02-03 16:59   ` David Welch
  0 siblings, 1 reply; 4+ messages in thread
From: Christian Ege @ 2014-02-03 16:28 UTC (permalink / raw)
  To: yocto

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

Hi,
> Hi,
>
> I am building an image for an embedded system using the chiefriver and 
> kernel 3.12.9.  I am using Ubuntu as our base system.
>
> The image builds and boots fine which is great but we have some 
> binaries built on Ubuntu which must run on the Yocto image.  When we 
> copy these across and try and run them we get a "File Not Found" error.
>
> Why would this be?  Doing file on our ubuntu executables we get:
>
> /bin/true: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
> dynamically linked (uses shared libs), for GNU/Linux 2.6.24, 
> BuildID[sha1]=0x2b45516be4a9f45b1127d54efb0d42e5f69b1c82, stripped
>
Just for the sake of completeness:
- Have you either copied the files to /usr/bin or using ./executable_name?
- Have you made a chmod+x executable_name before?

Sometimes transfering files over ftp in ASCII mode results in funny 
behaviours....

regrads,
Christian

> The Yocto executables are the same except instead of GNU/Linux 2.6.24 
> it is 2.6.16.  It that a problem?
>
> Also, on ubuntu we are running libc-2.17 but on Yocto it is libc-2.18. 
>  Is that a problem?
>
> Thanks for any assistance,
> Dave
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


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

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

* Re: File not found when trying to run an executable not build by Yocto
  2014-02-03 16:28 ` Christian Ege
@ 2014-02-03 16:59   ` David Welch
  2014-02-03 17:06     ` Gary Thomas
  0 siblings, 1 reply; 4+ messages in thread
From: David Welch @ 2014-02-03 16:59 UTC (permalink / raw)
  To: yocto

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

On Mon, Feb 3, 2014 at 4:28 PM, Christian Ege <k4230r6@gmail.com> wrote:

>  Hi,
>
> Hi,
>
>  I am building an image for an embedded system using the chiefriver and
> kernel 3.12.9.  I am using Ubuntu as our base system.
>
>  The image builds and boots fine which is great but we have some binaries
> built on Ubuntu which must run on the Yocto image.  When we copy these
> across and try and run them we get a "File Not Found" error.
>
>  Why would this be?  Doing file on our ubuntu executables we get:
>
>  /bin/true: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.6.24,
> BuildID[sha1]=0x2b45516be4a9f45b1127d54efb0d42e5f69b1c82, stripped
>
>   Just for the sake of completeness:
> - Have you either copied the files to /usr/bin or using ./executable_name?
> - Have you made a chmod+x executable_name before?
>

I was using ./.  The files are executable.


>
> Sometimes transfering files over ftp in ASCII mode results in funny
> behaviours....
>

Scp'ed so should be fine.


>
> regrads,
> Christian
>
>  The Yocto executables are the same except instead of GNU/Linux 2.6.24 it
> is 2.6.16.  It that a problem?
>
>  Also, on ubuntu we are running libc-2.17 but on Yocto it is libc-2.18.
>  Is that a problem?
>
>  Thanks for any assistance,
> Dave
>
>
> _______________________________________________
> yocto mailing listyocto@yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

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

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

* Re: File not found when trying to run an executable not build by Yocto
  2014-02-03 16:59   ` David Welch
@ 2014-02-03 17:06     ` Gary Thomas
  0 siblings, 0 replies; 4+ messages in thread
From: Gary Thomas @ 2014-02-03 17:06 UTC (permalink / raw)
  To: yocto

On 2014-02-03 09:59, David Welch wrote:
>
>
>
> On Mon, Feb 3, 2014 at 4:28 PM, Christian Ege <k4230r6@gmail.com <mailto:k4230r6@gmail.com>> wrote:
>
>     Hi,
>>     Hi,
>>
>>     I am building an image for an embedded system using the chiefriver and kernel 3.12.9.  I am using Ubuntu as our base system.
>>
>>     The image builds and boots fine which is great but we have some binaries built on Ubuntu which must run on the Yocto image.  When we copy these across and try and run them we
>>     get a "File Not Found" error.
>>
>>     Why would this be?  Doing file on our ubuntu executables we get:
>>
>>     /bin/true: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24,
>>     BuildID[sha1]=0x2b45516be4a9f45b1127d54efb0d42e5f69b1c82, stripped
>>
>     Just for the sake of completeness:
>     - Have you either copied the files to /usr/bin or using ./executable_name?
>     - Have you made a chmod+x executable_name before?
>
>
> I was using ./.  The files are executable.

Most likely cause is a missing library.  Try running 'ldd' on your file,
it should tell you what's missing if that's the case.

>
>
>     Sometimes transfering files over ftp in ASCII mode results in funny behaviours....
>
>
> Scp'ed so should be fine.
>
>
>     regrads,
>     Christian
>
>>     The Yocto executables are the same except instead of GNU/Linux 2.6.24 it is 2.6.16.  It that a problem?
>>
>>     Also, on ubuntu we are running libc-2.17 but on Yocto it is libc-2.18.  Is that a problem?
>>
>>     Thanks for any assistance,
>>     Dave

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


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

end of thread, other threads:[~2014-02-03 17:05 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-03 15:51 File not found when trying to run an executable not build by Yocto David Welch
2014-02-03 16:28 ` Christian Ege
2014-02-03 16:59   ` David Welch
2014-02-03 17:06     ` Gary Thomas

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.