All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ege <k4230r6@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: File not found when trying to run an executable not build by Yocto
Date: Mon, 03 Feb 2014 17:28:28 +0100	[thread overview]
Message-ID: <52EFC3AC.9030601@googlemail.com> (raw)
In-Reply-To: <CACP9YJccutcQq+j-1X0jabZK0KVvi+JJAj2ep2oicd59hJ5Xvg@mail.gmail.com>

[-- 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 --]

  reply	other threads:[~2014-02-03 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2014-02-03 16:59   ` David Welch
2014-02-03 17:06     ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52EFC3AC.9030601@googlemail.com \
    --to=k4230r6@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.