Sponsored Content
Full Discussion: Cannot execute binary file
Operating Systems Linux Fedora Cannot execute binary file Post 302856299 by fedora18 on Monday 23rd of September 2013 02:53:33 PM
Old 09-23-2013
Cannot execute binary file

Hi all,

Probably somewhat of an obvous problem here but i'm no pro.

I just bought a PengPod1000 at pengpod.com
On it I have an image of Fedora 18.

I am trying to run an application I wrote for Fedora 14 32 bit desktop on this tablet. With all permissions setup using chmod but I get "cannot execute binary file".

On the PengPod "uname -a" returns:
Linux localhost.localdomain 3.0.57+ #5 PREEMPT Mon May 13 09:10:40 CEST 2013 armv71 armv71 GNU/Linux

On my development computer "uname -a" returns:
Linux sensorbox2 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 i686 i386 GNU/Linux

On both systems "file myapp" returns:
myapp: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[shal]=0xeda499c66fce7811472888d5004ec6d45f56712f, not stripped

Other than the two kernels being different versions here the main difference is that the PengPod using the ARM architecture which I am very unfamiliar with.

Any ideas?


Thanks in advance!

---------- Post updated at 02:53 PM ---------- Previous update was at 02:52 PM ----------

the fedora image is at:

barrydegraaff.tk/2013/05/pengpod1000-fedora-18-xfce-armhf.html

Thanks in advance!
 

10 More Discussions You Might Find Interesting

1. Solaris

compiled binary file gives "cannot execute binary file"

Hi, I have two Solaris machines. 1. SunOS X 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-1500 2. SunOS Y 5.8 Generic_108528-13 sun4u sparc SUNW,Ultra-60 I am trying to buiild a project on both these machines. The Binary output file compiled on machine 2 runs on both the machines. Where... (0 Replies)
Discussion started by: scgupta
0 Replies

2. Linux

cannot execute binary file

We are getting one error when we execute the binary file below mentioned, and ownership goes to root:nobody, how to resolve this problem. sh /home/pub/bin/awk: cannot execute binary file :confused: Pls help me out . (2 Replies)
Discussion started by: durgaprasadr13
2 Replies

3. Solaris

How to execute a binary file in solaris?

How to execute a binary file in solaris? I used ./setup.bin . I got the error ./setup.bin not found. (4 Replies)
Discussion started by: agarwal
4 Replies

4. Shell Programming and Scripting

cannot execute binary file

HI, i am trying to execute one .bin file which is a pre-installed (not compiled by me). But I am getting the error "cannot execute binary file".I checked the permissions and everything is ok. also I checked ldd <bin-filename> andit showed a msg "not a dynamic executable" Can anyone help in... (4 Replies)
Discussion started by: bhag281
4 Replies

5. SuSE

can not execute binary file

When I am trying to execute a script created by Perl2exe in Linux SLES 8.1 running with virtual machine on mainframe s/390 ....I am getting "cannot execute binary file".... In the linux server which are not in mainframe the scripts are fine..... Thanks for help (1 Reply)
Discussion started by: Anu10
1 Replies

6. UNIX for Dummies Questions & Answers

Cannot execute binary file

As root, I receive the error message, "cannot execute binary file" when running some commands such as /usr/bin/clear or /usr/sbin/brctl or /usr/sbin/lsof. The system is running RHEL5.5. File permissions are 755. noexec is NOT set on the partitions where these files live. I've spent a... (6 Replies)
Discussion started by: SmithJ
6 Replies

7. Linux

Cannot execute binary file

I'm trying to install JasperReports Server 4.1 on Linux Ubuntu (release 11.04) as root and have following message: -bash: ./jasperreports-server-cp-4.1.0-linux-x64-installer.run: cannot execute binary file Is any idea what should I do in order to install Jasper? Previously, I installed... (6 Replies)
Discussion started by: pots06
6 Replies

8. UNIX for Dummies Questions & Answers

Xcrysden:Cannot execute binary file

Grettings, Hi and thanks for taking a look at this. I'm going to attempt to explain this the best I possible can but due to my limited knowledge of linux this may prove difficult. I have attempted to install xcrysden on cygwin following the instruction on xcrysden webpage (I attempted to link the... (2 Replies)
Discussion started by: Zbay
2 Replies

9. Shell Programming and Scripting

Cygwin - cannot execute binary file

Hey all, I am using Cygwin on a machine running windows 7 64bits. I am about to use the following command: $ faToTwoBit in.fa out.2bit In the manual on sourceforge it mentioned: "Download blat and faToTwoBit and set the blat_bin and fatotwobit_bin entries in config.txt to the fully... (4 Replies)
Discussion started by: @man
4 Replies

10. Red Hat

Cannot execute binary file

Hi, When i was trying to execute binary file i am getting the below " cannot execute binary file " error message." My Unix Version is : Red Hat Enterprise Linux Server release 5.1 (Tikanga) Logged in as Sudo user and $PATH Value is below ... (1 Reply)
Discussion started by: Nandy
1 Replies
SHTOOL-PLATFORM.TMP(1)					      GNU Portable Shell Tool					    SHTOOL-PLATFORM.TMP(1)

NAME
shtool-platform - GNU shtool Unix platform identification SYNOPSIS
shtool platform [-F|--format format] [-S|--sep string] [-C|--conc string] [-L|--lower] [-U|--upper] [-v|--verbose] [-c|--concise] [-n|--newline] [-d|--debug] [-t|--type type] [-n|--newline] [-d|--debug] DESCRIPTION
shtool platform is a flexible Unix platform identification program. It distinguishes a platform according to its hardware architecture and operating system. For both there is a class, product and technology identification. For each of those six identifications, there is a verbose, regular and concise version. This leads to eighteen (2x3x3) available identification strings for each platform, from which usually 2 are chosen in a particular situation. This is done by assembling the platform identification string using a format string containing one or more identification constructs of the forms ""%[xx]"" (verbose), ""%{xx}"" (regular) and ""%<xx>"" (concise). OPTIONS
The following command line options are available. -F, --format format This option controls the output formatting of this program. It is a plain-text string with the ""%"xx" constructs which expand to the various platform information strings. ""%{"xx"}"" is the canonical regular version of the information. ""%["xx"]"" is the verbose version of the information. ""%<"xx">"" is the concise version of the information. In total, the following constructs are available for expansion: %[ac] verbose hardware architecture class %{ac} regular hardware architecture class %<ac> concise hardware architecture class %[ap] verbose hardware architecture product %{ap} regular hardware architecture product %<ap> concise hardware architecture product %[at] verbose hardware architecture technology %{at} regular hardware architecture technology %<at> concise hardware architecture technology %[sc] verbose operating system class %{sc} regular operating system class %<sc> concise operating system class %[sp] verbose operating system product %{sp} regular operating system product %<sp> concise operating system product %[st] verbose operating system technology %{st} regular operating system technology %<st> concise operating system technology The default format string is ""%{sp} (%{ap})"", providing the regular operating system and hardware architecture product information. -S, --sep string This option sets the word separation string for the platform information strings. By default it is "" "" (whitespace). It is especially used for separating the operating system name and the operating system version. -C, --conc string This option sets the word concatenation string for the platform information strings. By default it is ""/"". It is especially used to concatenate multiple parts in operating system name and version parts. -L, --lower This options enforces conversion of the output to all lower case. -U, --upper This options enforces conversion of the output to all upper case. -v, --verbose This option enforces verbose versions of all expansion constructs in format string of option -F. It is equal to specifying all expansion constructs as ""%["xx"]"". -c, --concise This option enforces concise versions of all expansion constructs in format string of option -F. It is equal to specifying all expansion constructs as ""%<"xx">"". -n, --no-newline This option omits the usual trailing newline character in the output. -t, --type type This option is a meta option which internally sets options -F, -S, -C, -L, -U, -v or -c according to TYPE. It can be used to easily specify various commonly known outputs. The following TYPEs are available: binary Binary Package Id (OpenPKG RPM). This is equal to ""-F '%<ap"-%<sp>' -L -S '' -C '+'>" and results in outputs like ""ix86-freebsd4.9"" and ""ix86-debian3.0"". build Build-Time Checking (OpenPKG RPM). This is equal to ""-F '%<at"-%<st>' -L -S '' -C '+'>" and results in outputs like ""i686-freebsd4.9"" and ""i586-linux2.4"". gnu GNU config.guess Style Id. This is similar to build and is equal to ""-F '"%<at"-unknown-%<st>' -L -S '' -C '+'>" and results in outputs like ""i686-unknown-freebsd4.9"" and ""i586-unknown-linux2.4"". web HTTP Server Header Id. This is equal to ""-F '"%<sp"-%<ac>' -S '/' -C '+'>" and results in outputs like ""FreeBSD/4.9-iX86"" and ""Debian/3.0-iX86"". summary Human Readable Verbose Summary Information. This is equal to ""-F 'Class: %[sc] (%[ac]) Product: %[sp] (%[ap]) Technology: %[st] (%[at])' -S ' ' -C '/'"" and results in outputs like: Class: 4.4BSD (iX86) Product: FreeBSD 4.9-RC (iX86) Technology: FreeBSD 4.9-RC (i686) and Class: LSB (iX86) Product: Debian GNU/Linux 3.0 (iX86) Technology: GNU/Linux 2.2/2.4 (i686) all-in-one All-In-One Full-Table Information. This just outputs really all 2x2x3 identification strings as a table. -d, --debug This option enables some internal debugging messages. -V, --version This option outputs the version information of shtool platform only. -h, --help This option outputs the usage information of shtool platform only. EXAMPLE
The following real-life use cases are known: OpenPKG build-time decisions $ platform -c -L -S "" -C "+" -F "%at-%st" $ platform -c -L -S "" -C "+" -F "%ac-%sc" OpenPKG binary RPM packages $ platform -c -L -S "" -C "+" -F "%ap-%sp" README files $ platform -v -F "%sp (%ap)" $ platform -v -F "%sc (%ac)" Debugging $ platform --type=all-in-one SUPPORT
shtool platform currently knows the following particular Unix platforms in detail: FreeBSD, NetBSD, OpenBSD, Linux, Sun Solaris, SCO UnixWare, QNX Neutrino, SGI IRIX, HP HP-UX, HP Tru64, IBM AIX and Apple Mac OS X Darwin. All other Unix platforms are recognized through generic uname(1) information and so usually can be identified sufficiently, although the identification might be not as precise as possible. HISTORY
shtool platform was implemented in September 2003 by Ralf S. Engelschall for use in the OSSP and OpenPKG projects. It was prompted by the need in OpenPKG to have both product (for RPM filenames) and technology (for build-time decisions) identifiers for the Unix platforms, OpenPKG packages are maintained for. It was inspired by the GNU config.guess and the old GNU shtool guessos command. The major difference to GNU config.guess is that shtool platform does not use a vendor identification (cannot be determined most of the time and is not used at all in all projects I've ever seen) and is a lot more flexible (class, product and technology identifications combined with verbose, regular and concise outputs). The drawback of shtool platform is that it (still) knows less particular platforms, although the generic platform identification is sufficient enough most of the time. SEE ALSO
uname(3), GNU config.guess. 18-Jul-2008 shtool 2.0.8 SHTOOL-PLATFORM.TMP(1)
All times are GMT -4. The time now is 03:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy