cross gcc compiler on OpenSUSE


 
Thread Tools Search this Thread
Operating Systems Linux SuSE cross gcc compiler on OpenSUSE
# 1  
Old 03-04-2009
cross gcc compiler on OpenSUSE

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
cross-x86_64-binutils-2.18.50.20080409-12.1

cross-ia64-gcc-icecream-backend-4.3.1_20080507-7.1
cross-ia64-binutils-2.18.50.20080409-12.1

And what now?

I try create with mini howto, but i do not understand some step, and i get many errors :S
cross compiler mini howto
How to build an i386->Sparc Linux cross-compiler using GCC


Please help me.

BR
// Kolesar
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Programming

what is a cross compiler

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

2. UNIX for Dummies Questions & Answers

cc compiler and gcc compiler

hi, can we install gcc compiler in unix based OS(sun solar,IBM AIX,HP,etc) and also can we install sun cc compiler in AIX environment and vice versa. and more ..is linux support cc compiler regards Ajay (3 Replies)
Discussion started by: ajaysahoo
3 Replies

3. Linux

Building a ppc476 enabled GCC cross compiler and tool chain

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

4. UNIX for Advanced & Expert Users

Building a ppc476 enabled GCC cross compiler and tool chain

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

5. Red Hat

Building a ppc476 enabled GCC cross compiler and toolchain

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

6. Red Hat

installing the gcc cross compiler

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

7. Linux

GCC cross compiler for x86_64

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

8. Linux

GCC cross compiler for x86_64-elf

Hi, I am building GCC cross compiler for x86_64-elf for that a have followed steps, 1. mkdir build-gmp build-mpfr 2. cd build-gmp 3. ../gmp-4.2/configure --prefix=/usr/local 4. make all install 5. make check 6.cd ../build-mpfr 7. ../mpfr-2.3.2/configure... (5 Replies)
Discussion started by: Mandar123
5 Replies

9. UNIX for Dummies Questions & Answers

xl C/C++ compiler to GCC compiler

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
Login or Register to Ask a Question
dpkg-architecture(1)						  dpkg utilities					      dpkg-architecture(1)

NAME
dpkg-architecture - set and determine the architecture for package building SYNOPSIS
dpkg-architecture [options] [commands] DESCRIPTION
dpkg-architecture does provide a facility to determine and set the build and host architecture for package building. The build architecture is always determined by an external call to dpkg(1), and can not be set at the command line. You can specify the host architecture by providing one or both of the options -a and -t. The default is determined by an external call to gcc(1), or the same as the build architecture if CC or gcc are both not available. One out of -a and -t is sufficient, the value of the other will be set to a usable default. Indeed, it is often better to only specify one, because dpkg-architecture will warn you if your choice does not match the default. COMMANDS
-l Print the environment variables, one each line, in the format VARIABLE=value. This is the default action. -edebian-architecture Check for equality of architecture. By default debian-architecture is compared against the current Debian architecture, being the host. This action will not expand the architecture wildcards. Command finishes with an exit status of 0 if matched, 1 if not matched. -iarchitecture-wildcard Check for identity of architecture by expanding architecture-wildcard as an architecture wildcard and comparing against the current Debian architecture. Command finishes with an exit status of 0 if matched, 1 if not matched. -qvariable-name Print the value of a single variable. -s Print an export command. This can be used to set the environment variables using eval. -u Print a similar command to -s but to unset all variables. -c command Execute a command in an environment which has all variables set to the determined value. -L Print a list of valid architecture names. --help Show the usage message and exit. --version Show the version and exit. OPTIONS
-adebian-architecture Set the Debian architecture. -tgnu-system-type Set the GNU system type. -f Values set by existing environment variables with the same name as used by the scripts are honored (i.e. used by dpkg-architecture), except if this force flag is present. This allows the user to override a value even when the call to dpkg-architecture is buried in some other script (for example dpkg-buildpackage(1)). TERMS
build machine The machine the package is built on. host machine The machine the package is built for. Debian architecture The Debian architecture string, which specifies the binary tree in the FTP archive. Examples: i386, sparc, hurd-i386. architecture wildcard An architecture wildcard is a special architecture string that will match any real architecture being part of it. The general form is <kernel>-<cpu>. Examples: linux-any, any-i386, hurd-any. GNU system type An architecture specification string consisting of two parts separated by a dash: cpu and system. Examples: i386-linux-gnu, sparc-linux-gnu, i386-gnu, x86_64-netbsd. VARIABLES
The following variables are set by dpkg-architecture: DEB_BUILD_ARCH The Debian architecture of the build machine. DEB_BUILD_ARCH_OS The Debian system name of the build machine. DEB_BUILD_ARCH_CPU The Debian cpu name of the build machine. DEB_BUILD_ARCH_BITS The pointer size of the build machine (in bits). DEB_BUILD_ARCH_ENDIAN The endianness of the build machine (little / big). DEB_BUILD_GNU_CPU The CPU part of DEB_BUILD_GNU_TYPE. DEB_BUILD_GNU_SYSTEM The System part of DEB_BUILD_GNU_TYPE. DEB_BUILD_GNU_TYPE The GNU system type of the build machine. DEB_BUILD_MULTIARCH The clarified GNU system type of the build machine, used for filesystem paths. DEB_HOST_ARCH The Debian architecture of the host machine. DEB_HOST_ARCH_OS The Debian system name of the host machine. DEB_HOST_ARCH_CPU The Debian cpu name of the host machine. DEB_HOST_ARCH_BITS The pointer size of the host machine (in bits). DEB_HOST_ARCH_ENDIAN The endianness of the host machine (little / big). DEB_HOST_GNU_CPU The CPU part of DEB_HOST_GNU_TYPE. DEB_HOST_GNU_SYSTEM The System part of DEB_HOST_GNU_TYPE. DEB_HOST_GNU_TYPE The GNU system type of the host machine. DEB_HOST_MULTIARCH The clarified GNU system type of the host machine, used for filesystem paths. DEBIAN
/RULES The environment variables set by dpkg-architecture are passed to debian/rules as make variables (see make documentation). However, you should not rely on them, as this breaks manual invocation of the script. Instead, you should always initialize them using dpkg-architecture with the -q option. Here are some examples, which also show how you can improve the cross compilation support in your package: Instead of: ARCH=`dpkg --print-architecture` configure $(ARCH)-linux please use the following: DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) configure --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) Instead of: ARCH=`dpkg --print-architecture` ifeq ($(ARCH),alpha) ... endif please use: DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH) ifeq ($(DEB_HOST_ARCH),alpha) ... endif or if you only need to check the CPU or OS type, use the DEB_HOST_ARCH_CPU or DEB_HOST_ARCH_OS variables. In general, calling dpkg in the rules file to get architecture information is deprecated (unless you want to provide backward compatibil- ity, see below). Especially the --print-architecture option is unreliable since we have Debian architectures which don't equal a processor name. BACKWARD COMPATIBILITY
The DEB_*_ARCH_BITS and DEB_*_ARCH_ENDIAN variables were introduced in dpkg-dev 1.15.4. Using them in debian/rules thus requires a build- dependency on dpkg-dev (>= 1.15.4). The DEB_HOST_ARCH_CPU and DEB_HOST_ARCH_OS variables were introduced in dpkg-dev 1.13.2. Before this debian/rules files tended to check the values of the DEB_HOST_GNU_CPU or DEB_HOST_GNU_TYPE variables which have been subject to change. Where debian/rules files check these variables to decide how or what to compile, this should be updated to use the new variables and val- ues. You may wish to retain backwards compatibility with older version of dpkg-dev by using the following code: DEB_HOST_ARCH_CPU := $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU 2>/dev/null) DEB_HOST_ARCH_OS := $(shell dpkg-architecture -qDEB_HOST_ARCH_OS 2>/dev/null) # Take account of old dpkg-architecture output. ifeq ($(DEB_HOST_ARCH_CPU),) DEB_HOST_ARCH_CPU := $(shell dpkg-architecture -qDEB_HOST_GNU_CPU) ifeq ($(DEB_HOST_ARCH_CPU),x86_64) DEB_HOST_ARCH_CPU := amd64 endif endif ifeq ($(DEB_HOST_ARCH_OS),) DEB_HOST_ARCH_OS := $(subst -gnu,,$(shell dpkg-architecture -qDEB_HOST_GNU_SYSTEM)) ifeq ($(DEB_HOST_ARCH_OS),gnu) DEB_HOST_ARCH_OS := hurd endif endif And similarly for DEB_BUILD_ARCH_CPU and DEB_BUILD_ARCH_OS. If you still wish to support versions of dpkg-dev that did not include dpkg-architecture, the following does the job: DEB_BUILD_ARCH := $(shell dpkg --print-architecture) DEB_BUILD_GNU_CPU := $(patsubst hurd-%,%,$(DEB_BUILD_ARCH)) ifeq ($(filter-out hurd-%,$(DEB_BUILD_ARCH)),) DEB_BUILD_GNU_SYSTEM := gnu else DEB_BUILD_GNU_SYSTEM := linux-gnu endif DEB_BUILD_GNU_TYPE=$(DEB_BUILD_GNU_CPU)-$(DEB_BUILD_GNU_SYSTEM) DEB_HOST_ARCH := $(DEB_BUILD_ARCH) DEB_HOST_GNU_CPU := $(DEB_BUILD_GNU_CPU) DEB_HOST_GNU_SYSTEM := $(DEB_BUILD_GNU_SYSTEM) DEB_HOST_GNU_TYPE := $(DEB_BUILD_GNU_TYPE) Put a subset of these lines at the top of your debian/rules file; these default values will be overwritten if dpkg-architecture is used. You don't need the full set. Choose a consistent set which contains the values you use in the rules file. For example, if you only need the host Debian architecture, `DEB_HOST_ARCH=`dpkg --print-architecture`' is sufficient (this is indeed the Debian architecture of the build machine, but remember that we are only trying to be backward compatible with native compilation). The -e and -i options were only introduced in relatively recent versions of dpkg-architecture (since dpkg 1.13.13). EXAMPLES
dpkg-buildpackage accepts the -a option and passes it to dpkg-architecture. Other examples: CC=i386-gnu-gcc dpkg-architecture -c debian/rules build eval `dpkg-architecture -u` Check if an architecture is equal to the current architecture or a given one: dpkg-architecture -elinux-alpha dpkg-architecture -amips -elinux-mips Check if the current architecture or an architecture provided with -a are Linux systems: dpkg-architecture -ilinux-any dpkg-architecture -ai386 -ilinux-any FILES
All these files have to be present for dpkg-architecture to work. Their location can be overridden at runtime with the environment variable DPKG_DATADIR. /usr/share/dpkg/cputable Table of known CPU names and mapping to their GNU name. /usr/share/dpkg/ostable Table of known operating system names and mapping to their GNU name. /usr/share/dpkg/triplettable Mapping between Debian architecture triplets and Debian architecture names. SEE ALSO
dpkg-buildpackage(1), dpkg-cross(1). AUTHOR
dpkg-architecture and this man page were initially written by Marcus Brinkmann <brinkmd@debian.org>. Debian Project 2009-08-15 dpkg-architecture(1)