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 suite						      dpkg-architecture(1)

NAME
dpkg-architecture - set and determine the architecture for package building SYNOPSIS
dpkg-architecture [option...] [command] DESCRIPTION
dpkg-architecture provides 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 cannot be set at the command line. You can specify the host architecture by providing one or both of the options --host-arch and --host-type. 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 --host-arch and --host-type 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, --list Print the environment variables, one each line, in the format VARIABLE=value. This is the default action. -e, --equal architecture Check for equality of architecture (since dpkg 1.13.13). It compares the current or specified Debian host architecture against architecture, to check if they are equal. This action will not expand the architecture wildcards. Command finishes with an exit status of 0 if matched, 1 if not matched. -i, --is architecture-wildcard Check for identity of architecture (since dpkg 1.13.13). It compares the current or specified Debian host architecture against architecture-wildcard after having expanded it as an architecture wildcard, to check if they match. Command finishes with an exit status of 0 if matched, 1 if not matched. -q, --query variable-name Print the value of a single variable. -s, --print-set Print an export command. This can be used to set the environment variables using eval. -u, --print-unset Print a similar command to --print-unset but to unset all variables. -c, --command command-string Execute a command-string in an environment which has all variables set to the determined value. -L, --list-known Print a list of valid architecture names. Possibly restricted by one or more of the matching options --match-wildcard, --match-bits or --match-endian (since dpkg 1.17.14). -?, --help Show the usage message and exit. --version Show the version and exit. OPTIONS
-a, --host-arch architecture Set the host Debian architecture. -t, --host-type gnu-system-type Set the host GNU system type. -A, --target-arch architecture Set the target Debian architecture (since dpkg 1.17.14). -T, --target-type gnu-system-type Set the target GNU system type (since dpkg 1.17.14). -W, --match-wildcard architecture-wildcard Restrict the architectures listed by --list-known to ones matching the specified architecture wildcard (since dpkg 1.17.14). -B, --match-bits architecture-bits Restrict the architectures listed by --list-known to ones with the specified CPU bits (since dpkg 1.17.14). Either 32 or 64. -E, --match-endian architecture-endianness Restrict the architectures listed by --list-known to ones with the specified endianness (since dpkg 1.17.14). Either little or big. -f, --force 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. target machine The machine the compiler is building for. This is only needed when building a cross-toolchain, one that will be built on the build architecture, to be run on the host architecture, and to build code for the target architecture. Debian architecture The Debian architecture string, which specifies the binary tree in the FTP archive. Examples: i386, sparc, hurd-i386. Debian architecture tuple A Debian architecture tuple is the fully qualified architecture with all its components spelled out. This differs with Debian architectures in that at least the cpu component does not embed the abi. The current tuple has the form abi-libc-os-cpu. Examples: base-gnu-linux-amd64, eabihf-musl-linux-arm. Debian architecture wildcard A Debian architecture wildcard is a special architecture string that will match any real architecture being part of it. The general form is a Debian architecture tuple with four or less elements, and with at least one of them being any. Missing elements of the tuple are prefixed implicitly as any, and thus the following pairs are equivalent: any-any-any-any = any any-any-os-any = os-any any-libc-any-any = libc-any-any Examples: linux-any, any-i386, hurd-any, eabi-any-any-arm, musl-any-any. GNU system type An architecture specification string consisting of two parts separated by a hyphen: cpu and system. Examples: i586-linux-gnu, sparc-linux-gnu, i686-gnu, x86_64-netbsd. multiarch triplet The clarified GNU system type, used for filesystem paths. This triplet does not change even when the baseline ISA gets bumped, so that the resulting paths are stable over time. The only current difference with the GNU system type is that the CPU part for i386 based systems is always i386. Examples: i386-linux-gnu, x86_64-linux-gnu. Example paths: /lib/powerpc64le-linux-gnu/, /usr/lib/i386-kfreebsd-gnu/. VARIABLES
The following variables are set by dpkg-architecture: DEB_BUILD_ARCH The Debian architecture of the build machine. DEB_BUILD_ARCH_ABI The Debian abi name of the build machine (since dpkg 1.18.11). DEB_BUILD_ARCH_LIBC The Debian libc name of the build machine (since dpkg 1.18.11). DEB_BUILD_ARCH_OS The Debian system name of the build machine (since dpkg 1.13.2). DEB_BUILD_ARCH_CPU The Debian cpu name of the build machine (since dpkg 1.13.2). DEB_BUILD_ARCH_BITS The pointer size of the build machine (in bits; since dpkg 1.15.4). DEB_BUILD_ARCH_ENDIAN The endianness of the build machine (little / big; since dpkg 1.15.4). 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 (since dpkg 1.16.0). DEB_HOST_ARCH The Debian architecture of the host machine. DEB_HOST_ARCH_ABI The Debian abi name of the host machine (since dpkg 1.18.11). DEB_HOST_ARCH_LIBC The Debian libc name of the host machine (since dpkg 1.18.11). DEB_HOST_ARCH_OS The Debian system name of the host machine (since dpkg 1.13.2). DEB_HOST_ARCH_CPU The Debian cpu name of the host machine (since dpkg 1.13.2). DEB_HOST_ARCH_BITS The pointer size of the host machine (in bits; since dpkg 1.15.4). DEB_HOST_ARCH_ENDIAN The endianness of the host machine (little / big; since dpkg 1.15.4). 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 (since dpkg 1.16.0). DEB_TARGET_ARCH The Debian architecture of the target machine (since dpkg 1.17.14). DEB_TARGET_ARCH_ABI The Debian abi name of the target machine (since dpkg 1.18.11). DEB_TARGET_ARCH_LIBC The Debian libc name of the target machine (since dpkg 1.18.11). DEB_TARGET_ARCH_OS The Debian system name of the target machine (since dpkg 1.17.14). DEB_TARGET_ARCH_CPU The Debian cpu name of the target machine (since dpkg 1.17.14). DEB_TARGET_ARCH_BITS The pointer size of the target machine (in bits; since dpkg 1.17.14). DEB_TARGET_ARCH_ENDIAN The endianness of the target machine (little / big; since dpkg 1.17.14). DEB_TARGET_GNU_CPU The CPU part of DEB_TARGET_GNU_TYPE (since dpkg 1.17.14). DEB_TARGET_GNU_SYSTEM The System part of DEB_TARGET_GNU_TYPE (since dpkg 1.17.14). DEB_TARGET_GNU_TYPE The GNU system type of the target machine (since dpkg 1.17.14). DEB_TARGET_MULTIARCH The clarified GNU system type of the target machine, used for filesystem paths (since dpkg 1.17.14). FILES
Architecture tables 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. These tables contain a format Version pseudo-field on their first line to mark their format, so that parsers can check if they understand it, such as "# Version=1.0". /usr/share/dpkg/cputable Table of known CPU names and mapping to their GNU name. Format version 1.0 (since dpkg 1.13.2). /usr/share/dpkg/ostable Table of known operating system names and mapping to their GNU name. Format version 2.0 (since dpkg 1.18.11). /usr/share/dpkg/tupletable Mapping between Debian architecture tuples and Debian architecture names. Format version 1.0 (since dpkg 1.18.11). /usr/share/dpkg/abitable Table of Debian architecture ABI attribute overrides. Format version 2.0 (since dpkg 1.18.11). Packaging support /usr/share/dpkg/architecture.mk Makefile snippet that properly sets and exports all the variables that dpkg-architecture outputs (since dpkg 1.16.1). 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 the current or specified host architecture is equal to an architecture: dpkg-architecture -elinux-alpha dpkg-architecture -amips -elinux-mips Check if the current or specified host architecture is a Linux system: dpkg-architecture -ilinux-any dpkg-architecture -ai386 -ilinux-any Usage in 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: Retrieving the GNU system type and forwarding it to ./configure: DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) [...] ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE)) confflags += --build=$(DEB_HOST_GNU_TYPE) else confflags += --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) endif [...] ./configure $(confflags) Doing something only for a specific architecture: 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. Note that you can also rely on an external Makefile snippet to properly set all the variables that dpkg-architecture can provide: include /usr/share/dpkg/architecture.mk ifeq ($(DEB_HOST_ARCH),alpha) [...] endif In any case, you should never use dpkg --print-architecture to get architecture information during a package build. ENVIRONMENT
DPKG_DATADIR If set, it will be used as the dpkg data directory, where the architecture tables are located (since dpkg 1.14.17). Defaults to <</usr/share/dpkg>>. NOTES
All long command and option names available only since dpkg 1.17.17. SEE ALSO
dpkg-buildpackage(1). 1.19.0.5 2018-04-16 dpkg-architecture(1)