From: David Laight <David.Laight@ACULAB.COM>
To: 'Baruch Siach' <baruch@tkos.co.il>,
Ugroon} Hackerone <h1ugroon@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] How to run an executable file
Date: Fri, 20 May 2022 10:17:35 +0000 [thread overview]
Message-ID: <55a1dc0b3ba345a6adb4e98c0faf5353@AcuMS.aculab.com> (raw)
In-Reply-To: <87czg8n55k.fsf@tarshish>
From: Baruch Siach
> Sent: 20 May 2022 06:25
>
> On Fri, May 20 2022, Ugroon} Hackerone wrote:
> > I have an executable file and when I try to run it with "chmod +x
> > file" and "./file" I'm getting command not found: ./file error. So I
> > just want to learn how to execute this file?
> >
> > Note: The output of "file file" is Elf x64
>
> The most common reason for "not found" error on running an executable is
> that one or more of needed shared library is missing. The command
>
> readelf -d file
>
> will list the needed libraries, as well as more information on the
> dynamic section of the ELF executable. Make sure you have all listed
> shared libraries.
You can also be missing the required 'elf interpreter'.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-05-20 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 5:22 [Buildroot] How to run an executable file Ugroon} Hackerone
2022-05-20 5:24 ` Baruch Siach via buildroot
2022-05-20 10:17 ` David Laight [this message]
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=55a1dc0b3ba345a6adb4e98c0faf5353@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=baruch@tkos.co.il \
--cc=buildroot@buildroot.org \
--cc=h1ugroon@gmail.com \
/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.