06-22-2009
Given that we do not know what you changed to support cross-compiling to ARM, it is difficult to give precise information. Perhaps the easiest way would be to remove and re-install gcc using yum.
If you want to do it by hand, you probably need to remove the --target option from gcc configuration, and reinstall the correct bintools and GNU assembler for Fedora 9 and point to the correct crt0 unless you used newlib.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello!
I have an entry on my crontab.
10 00 * * * /bscsprod/bscs/prod/523/bin/tehcron.sh
$ /bscsprod/bscs/prod/523/bin/vi tehcron.sh
nohup teh -t -f > /dev/null &
~
~
~
~
~
~
~
~
"tehcron.sh" 13 lines, 365 characters
but executing the script from the... (5 Replies)
Discussion started by: Tris
5 Replies
2. Linux
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?
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
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
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
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
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
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. Fedora
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... (7 Replies)
Discussion started by: fedora18
7 Replies
10. Red Hat
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
LINUX(4) BSD Kernel Interfaces Manual LINUX(4)
NAME
linux -- Linux ABI support
SYNOPSIS
To compile support for this ABI into an i386 kernel place the following line in your kernel configuration file:
options COMPAT_LINUX
for an amd64 kernel use:
options COMPAT_LINUX32
Alternatively, to load the ABI as a module at boot time, place the following line in loader.conf(5):
linux_load="YES"
DESCRIPTION
The linux module provides limited Linux ABI (application binary interface) compatibility for userland applications. The module provides the
following significant facilities:
o An image activator for correctly branded elf(5) executable images
o Special signal handling for activated images
o Linux to native system call translation
It is important to note that the Linux ABI support it not provided through an emulator. Rather, a true (albeit limited) ABI implementation
is provided.
The following sysctl(8) tunable variables are available:
compat.linux.osname Linux kernel operating system name.
compat.linux.osrelease Linux kernel operating system release. Changing this to something else is discouraged on non-development systems,
because it may change the way Linux programs work. Recent versions of GNU libc are known to use different syscalls
depending on the value of this sysctl.
compat.linux.oss_version Linux Open Sound System version.
The linux module can be linked into the kernel statically with the COMPAT_LINUX kernel configuration option or loaded as required. The fol-
lowing command will load the module if it is neither linked into the kernel nor already loaded as a module:
if ! kldstat -v | grep -E 'linux(aout|elf)' > /dev/null; then
kldload linux > /dev/null 2>&1
fi
Note that dynamically linked Linux executables will require a suitable environment in /compat/linux. Specifically, the Linux run-time
linker's hints files should be correctly initialized. For this reason, it is common to execute the following commands to prepare the system
to correctly run Linux executables:
if [ -x /compat/linux/sbin/ldconfig ]; then
/compat/linux/sbin/ldconfig -r /compat/linux
fi
For information on loading the linux kernel loadable module automatically on system startup, see rc.conf(5). This information applies
regardless of whether the linux module is statically linked into the kernel or loaded as a module.
FILES
/compat/linux minimal Linux run-time environment
/compat/linux/proc limited Linux process file system
/compat/linux/sys limited Linux system file system
SEE ALSO
brandelf(1), elf(5), linprocfs(5), linsysfs(5)
HISTORY
Linux ABI support first appeared in FreeBSD 2.1.
BSD February 8, 2010 BSD