Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nathanael D. Noblet <nathanael@gnat.ca>
To: buildroot@busybox.net
Subject: [Buildroot] ### Executing FIles
Date: Wed, 27 Aug 2008 08:59:25 -0600	[thread overview]
Message-ID: <48B56BCD.2000101@gnat.ca> (raw)
In-Reply-To: <46a136670808261706v1335cea6g60889e0262ac00bf@mail.gmail.com>

John Voltz wrote:
> On Tue, Aug 26, 2008 at 6:42 PM, Steve Spano <steve@fl-eng.com 
> <mailto:steve@fl-eng.com>> wrote:
> 
>     Hello
> 
>     I am stumped on this issue
> 
>     I have a buildroot filesystem running and I cannot seem to execute
>     new files
>     that I have placed on it.
> 
>     For example, I upload a new executable file that I compile on a host PC.
>     I change its permissions to execute and I type "./myfile"
>     It comes back saying "-sh: myfile not found"
>     BUT, I can vi the file, I can copy it, delete it /etc/etc
>     If I change its permissions to read-only and then try to execute it, the
>     shell tells me "permission denied".

If you are executing a shell script, I've seen that error before when 
there were hidden utf-8 marks or dos line feeds in the first line.

I think I've also seen it when you compile a program and link it against 
  glibc and then try to run it against uclibc. It can't load the loader 
portion of the C library I think. Otherwise other missing linked library 
files typically provide an error message about 'unable to load libxxx.so'


-- 
Nathanael d. Noblet
Gnat Solutions, Inc
T: 403.875.4613

  reply	other threads:[~2008-08-27 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 22:37 [Buildroot] svn commit: trunk/buildroot/package/atk jacmet at uclibc.org
2008-08-26 22:42 ` [Buildroot] ### Executing FIles Steve Spano
2008-08-27  0:06   ` John Voltz
2008-08-27 14:59     ` Nathanael D. Noblet [this message]
2008-08-27 20:55       ` Steve Spano
2008-08-27  0:11   ` Hebbar
2008-08-27  1:05     ` Steve Spano

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=48B56BCD.2000101@gnat.ca \
    --to=nathanael@gnat.ca \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox