01-01-2009
I do not have specific experience with this, but as I said in my first post, in order to make any cross compiler work, you must also install all cross-platform libraries, header files, etc. This includes the "stub object" .o files that gcc is currently requiring. Again, look at the documentation carefully to determine what steps are required for installing the support libraries and object files.
However you compile it, the linker still needs to find the static or dynamic objects which will be used to ultimately execute the program. This means you have to have all 64-bit libraries installed upon which the program depends. Apparently, then, before you cross-compile a program, you must install all supporting libraries, or cross compile them. Installing would be much easier.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
we are converting from IBM-AIX(xl c/c++ compiler) to Linux(GCC complier).
As a part of this i need to change the CFLAGS.
The xl c/c++ complier CFLAGS is
CFLAGS := $(CDEBUG) $(PROJECT_INCLUDE_DIRS) $(COBJECT_MODE) -qcpluscmt -qmakedep -qcheck=all \
-qalign=bit_packed $(LINT_FLAGS)... (0 Replies)
Discussion started by: pbattu1
0 Replies
2. Linux
Hi
I compiled a hello world program on two different 64-bit Linux machines, named quimby and node0331. When I compile on quimby and run on node0331 I get a "Floating exception (core dumped)" error. But if I do it in reverse, things work fine.
Here's my compilation on quimby:
$ uname -a... (3 Replies)
Discussion started by: same1290
3 Replies
3. Linux
Hi,
I am tried to install GCC cross compiler for 64-bit machine.
i want compile one application for 64 bit machine.
I have followed steps form GCC Cross-Compile - OSDev Wiki .
Please if anybody have installed cross compiler successfully, please tell me the steps followed by you.
Thanking... (0 Replies)
Discussion started by: Mandar123
0 Replies
4. SuSE
Hi All
I want to create build machine for three architecture (i386, amd64 and ia64) on 32bit machine on OpenSUSE 10.0
I installed:
cross-i386-gcc-icecream-backend-4.3.1_20080507-7.1
cross-i386-binutils-2.18.50.20080409-12.1
cross-x86_64-gcc-icecream-backend-4.3.1_20080507-7.1... (0 Replies)
Discussion started by: Kolesar
0 Replies
5. Red Hat
While i try to install the gcc cross compiler using following commands in fedora 6
commands
cd /etc/yum.repos.d/
# wget http://fedora-arm.wantstofly.org/cross/cross.repo
# yum install armv5tel-redhat-linux-gnueabi-gcc
i got an error
# cd yum.repos.d
# wget... (3 Replies)
Discussion started by: sujith4u87
3 Replies
6. Red Hat
Building a ppc476 enabled GCC cross compiler and tool chain
Hello,
I am trying to build a cross GCC compiler for PPC476.
I applied all the relevant patches. Cross compiler build was successful.
When i try to compile the source code using the cross compiler i am getting the below error... (0 Replies)
Discussion started by: raghuhb
0 Replies
7. UNIX for Advanced & Expert Users
Building a ppc476 enabled GCC cross compiler and tool chain
Hello,
I am trying to build a cross GCC compiler for PPC476.
I applied all the relevant patches. Cross compiler build was successful.
When i try to compile the source code using the cross compiler i am getting the below error... (1 Reply)
Discussion started by: raghuhb
1 Replies
8. Linux
Building a ppc476 enabled GCC cross compiler and tool chain
Hello,
I am trying to build a cross GCC compiler for PPC476.
I applied all the relevant patches. Cross compiler build was successful.
When i try to compile the source code using the cross compiler i am getting the below error... (1 Reply)
Discussion started by: raghuhb
1 Replies
9. Programming
recently i was been to an interview to an automotive company, they have posed me a question that what section of compiler must be changed if the target is changed.
ie,if ur compiler is meant for generating executable to a 8051 target what changes do you do to make it flexible to generate the... (2 Replies)
Discussion started by: shyam.sunder91
2 Replies
LEARN ABOUT CENTOS
execstack
execstack(8) System Manager's Manual execstack(8)
NAME
execstack - tool to set, clear, or query executable stack flag of ELF binaries and shared libraries
SYNOPSIS
execstack [OPTION...] [FILES]
DESCRIPTION
execstack is a program which sets, clears, or queries executable stack flag of ELF binaries and shared libraries. Linux has in the past
allowed execution of instructions on the stack and there are lots of binaries and shared libraries assuming this behaviour. Furthermore,
GCC trampoline code for e.g. nested functions requires executable stack on many architectures. To avoid breaking binaries and shared
libraries which need executable stack, ELF binaries and shared libraries now can be marked as requiring executable stack or not requiring
it. This marking is done through the p_flags field in the PT_GNU_STACK program header entry. If the marking is missing, kernel or dynamic
linker need to assume it might need executable stack. The marking is done automatically by recent GCC versions (objects using trampolines
on the stack are marked as requiring executable stack, all other newly built objects are marked as not requiring it) and linker collects
these markings into marking of the whole binary or shared library. The user can override this at assembly time (through --execstack or
--noexecstack assembler options), at link time (through -z execstack or -z noexecstack linker options) and using the execstack tool also on
an already linker binary or shared library. This tool is especially useful for third party shared libraries where it is known that they
don't need executable stack or testing proves it.
OPTIONS
-s --set-execstack
Mark binary or shared library as requiring executable stack.
-c --clear-execstack
Mark binary or shared library as not requiring executable stack.
-q --query
Query executable stack marking of binaries and shared libraries. For each file it prints either - when executable stack is not
required, X when executable stack is required or ? when it is unknown whether the object requires or doesn't require executable
stack (the marking is missing).
-V Print execstack version and exit.
-? --help
Print help message.
--usage
Print a short usage message.
ARGUMENTS
Command line arguments should be names of ELF binaries and shared libraries which should be modified or queried.
EXAMPLES
# execstack -s ~/lib/libfoo.so.1
will mark ~/lib/libfoo.so.1 as requiring executable stack.
# execstack -c ~/bin/bar
will mark ~/bin/bar as not requiring executable stack.
# execstack -q ~/lib/libfoo.so.1 ~/bin/bar
will query executable stack marking of the given files.
SEE ALSO
ld.so(8).
BUGS
execstack doesn't support yet marking of executables if they do not have PT_GNU_STACK program header entry nor they have room for program
segment header table growth.
AUTHORS
Jakub Jelinek <jakub@redhat.com>.
28 October 2003 execstack(8)