* canadian build @ 2015-10-22 2:39 Randy Yates 2015-10-22 2:41 ` Randy Yates 0 siblings, 1 reply; 10+ messages in thread From: Randy Yates @ 2015-10-22 2:39 UTC (permalink / raw) To: crossgcc Hi, I have successfully built a non-canadian toolchain with build/host equivalent to fedora 21 linux and the target equal to the motorola m68k. I would like to do a canadian build as follows: build = fedora 21 linux host = cygwin/windows (32-bit) target = motorola m68k I have read the FAQ on this and looked through all the options, but I don't exactly get how to do this. I was able to specify the canadian build type, but I don't see where you specify the host. Can someone please help? -- Randy Yates Digital Signal Labs http://www.digitalsignallabs.com -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2015-10-22 2:39 canadian build Randy Yates @ 2015-10-22 2:41 ` Randy Yates 0 siblings, 0 replies; 10+ messages in thread From: Randy Yates @ 2015-10-22 2:41 UTC (permalink / raw) To: crossgcc PS: This is crosstool-NG 1.21.0. Randy Yates <yates@digitalsignallabs.com> writes: > Hi, > > I have successfully built a non-canadian toolchain with build/host > equivalent to fedora 21 linux and the target equal to the motorola m68k. > > I would like to do a canadian build as follows: > > build = fedora 21 linux > host = cygwin/windows (32-bit) > target = motorola m68k > > I have read the FAQ on this and looked through all the options, but > I don't exactly get how to do this. I was able to specify the > canadian build type, but I don't see where you specify the host. > > Can someone please help? -- Randy Yates Digital Signal Labs http://www.digitalsignallabs.com -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* canadian build @ 2012-03-07 19:01 Tobias Arp 2012-03-07 19:37 ` Samuel Martin ` (2 more replies) 0 siblings, 3 replies; 10+ messages in thread From: Tobias Arp @ 2012-03-07 19:01 UTC (permalink / raw) To: crossgcc Hi, i try to do a canadian build with crosstool-ng 1.14.1. Build=i686-pc-linux-gnu Host=i586-pc-linux-gnu Target=arm What do i have to put in *** Build system *** -> Tuple and in *** Host system *** Tuple. When i add this for the build system: i686-pc-linux-gnu and this for the host: i586-pc-linux-gnu I get this error: [INFO ] Performing some trivial sanity checks [INFO ] Build started 20120307.200018 [INFO ] Building environment variables [WARN ] Directory '/home/tobias/src' does not exist. [WARN ] Will not save downloaded tarballs to local storage. [EXTRA] Preparing working directories [ERROR] Missing: 'i586-pc-linux-gnu-ar' or 'i586-pc-linux-gnu-ar' or 'ar' : either needed! [00:01] / make: *** [build] Fehler 1 Best regards Tobias ___________________________________________________________ Ihr WEB.DE Postfach immer dabei: die kostenlose WEB.DE Mail App für iPhone und Android. https://produkte.web.de/freemail_mobile_startseite/ -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-07 19:01 Tobias Arp @ 2012-03-07 19:37 ` Samuel Martin 2012-03-07 20:17 ` Yann E. MORIN 2012-03-08 7:49 ` Per Arnold Blaasmo 2012-03-08 9:47 ` Thomas Petazzoni 2 siblings, 1 reply; 10+ messages in thread From: Samuel Martin @ 2012-03-07 19:37 UTC (permalink / raw) To: Tobias Arp; +Cc: crossgcc Hi Tobias, all, > I get this error: > > [INFO ] Performing some trivial sanity checks > [INFO ] Build started 20120307.200018 > [INFO ] Building environment variables > [WARN ] Directory '/home/tobias/src' does not exist. > [WARN ] Will not save downloaded tarballs to local storage. > [EXTRA] Preparing working directories > [ERROR] Missing: 'i586-pc-linux-gnu-ar' or 'i586-pc-linux-gnu-ar' or 'ar' : either needed! > [00:01] / make: *** [build] Fehler 1 > Last week, building canadian cross-compiler using the head/top of the crosstool-NG repository, i got the same error. I did find a bug in: script/crosstool-NG.sh Quick fix is: sed -e 's/CT_TTOLCHAIN_TYPE/CT_TOOLCHAIN_TYPE/' \ -i script/crosstool-NG.sh I have some patches in my queue, but they need to be cleaned up before submission. It seems that there is another bug at least about build-system-prefix and/or the host one. To quickly fix this (i was/am a bit in the rush), i added the bin directory for both the build-to-host cross-compiler and the build-to-target one to my PATH and correctly set the build-system-tuple as well as the host-system-tuple. So you need to have these 2 cross-compilers built before starting the canadian. Have a look at: http://sourceware.org/ml/crossgcc/2011-03/msg00069.html Regards, Sam -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-07 19:37 ` Samuel Martin @ 2012-03-07 20:17 ` Yann E. MORIN 2012-03-08 7:48 ` Tobias Arp 0 siblings, 1 reply; 10+ messages in thread From: Yann E. MORIN @ 2012-03-07 20:17 UTC (permalink / raw) To: crossgcc; +Cc: Samuel Martin, Tobias Arp Tobias, Samuel, All, On Wednesday 07 March 2012 20:36:41 Samuel Martin wrote: > Last week, building canadian cross-compiler using the head/top of the > crosstool-NG repository, > i got the same error. > I did find a bug in: script/crosstool-NG.sh > Quick fix is: > sed -e 's/CT_TTOLCHAIN_TYPE/CT_TOOLCHAIN_TYPE/' \ > -i script/crosstool-NG.sh I just greped for TTOLCHAIN in 1.14 and current tree, and found no match at all: $ hg grep --follow TTOLCHAIN |wc -l 0 What tree are you speaking about? Are you using a pristine tree, or do you have local patches? > It seems that there is another bug at least about build-system-prefix > and/or the host one. > To quickly fix this (i was/am a bit in the rush), i added the bin > directory for both the > build-to-host cross-compiler and the build-to-target one to my PATH > and correctly set the > build-system-tuple as well as the host-system-tuple. There are two ways you can handle this: 1- enter only the tuple- name of the two cross-compilers, and them in the PATH, as you did, eg.: CT_HOST_PREFIX="arm-unknown-linux-gnueabi-" CT_TARGET_PREFIX="mips-unknwon-linux-gnu-" PATH="/path/to/arm-compiler/bin:/path/to/mips-compiler:${PATH}" 2- enter the fully qualified path to your compiler, so there is no need to change your PATH, eg.: CT_HOST_PREFIX="/path/to/arm-compiler/bin/arm-unknown-linux-gnueabi-" CT_TARGET_PREFIX="/path/to/mips-compiler/mips-unknwon-linux-gnu-" > So you need to have these 2 cross-compilers built before starting the canadian. Yes, currently the canadian infrastrucutre requires that two cross-compiler pre-exist: - the build->host cross-compiler, to be able to build the tools that will ultimately run on host (gcc, binutils...) - the build->target cross-compiler, to be able to build the libraries and tools that will ultimately run on the target (glibc, libgcc...) > Have a look at: http://sourceware.org/ml/crossgcc/2011-03/msg00069.html This thread is about the on-going revamp of the canadian infrastructure (yes, it's been on-going for that long, even much longer...). It does not really apply in this case... Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-07 20:17 ` Yann E. MORIN @ 2012-03-08 7:48 ` Tobias Arp 0 siblings, 0 replies; 10+ messages in thread From: Tobias Arp @ 2012-03-08 7:48 UTC (permalink / raw) To: Yann E. MORIN; +Cc: crossgcc, Samuel Martin Yann, i am still not able to build the canadian cross compiler. I have both cross compiler (build -> host and build ->target) My config file (the part with CT_HOST_PREFIX...) is this: # CT_NATIVE is not set # CT_CROSS is not set # CT_CROSS_NATIVE is not set CT_CANADIAN=y CT_TOOLCHAIN_TYPE="canadian" # # Build system # CT_BUILD="" CT_BUILD_PREFIX="" CT_BUILD_SUFFIX="" # # Host system # CT_HOST="" CT_HOST_PREFIX="/home/tobias/x-tools/i586-pc-linux-gnu/bin/i586-pc-linux-gnu-" CT_HOST_SUFFIX="" # # Target system # CT_TARGET_PREFIX="/home/tobias/x-tools/arm-i686-linux-gnueabi/bin/arm-linux-" CT_TARGET_SUFFIX="" I am getting now this error: [INFO ] Performing some trivial sanity checks [INFO ] Build started 20120308.083859 [INFO ] Building environment variables [EXTRA] Preparing working directories [00:01] / Invalid configuration `': machine `' not recognized [ERROR] [ERROR] >> [ERROR] >> Build failed in step '(top-level)' [ERROR] >> [ERROR] >> Error happened in: CT_DoConfigSub[scripts/functions@940] [ERROR] >> called from: main[scripts/crosstool-NG.sh@372] [ERROR] >> [ERROR] >> For more info on this error, look at the file: 'build.log' [ERROR] >> There is a list of known issues, some with workarounds, in: [ERROR] >> 'docs/B - Known issues.txt' [ERROR] [ERROR] (elapsed: 0:01.14) Best regards Tobias Am 07.03.2012 21:16, schrieb Yann E. MORIN: > Tobias, Samuel, All, > > On Wednesday 07 March 2012 20:36:41 Samuel Martin wrote: >> Last week, building canadian cross-compiler using the head/top of the >> crosstool-NG repository, >> i got the same error. >> I did find a bug in: script/crosstool-NG.sh >> Quick fix is: >> sed -e 's/CT_TTOLCHAIN_TYPE/CT_TOOLCHAIN_TYPE/' \ >> -i script/crosstool-NG.sh > I just greped for TTOLCHAIN in 1.14 and current tree, and found > no match at all: > $ hg grep --follow TTOLCHAIN |wc -l > 0 > > What tree are you speaking about? > Are you using a pristine tree, or do you have local patches? > >> It seems that there is another bug at least about build-system-prefix >> and/or the host one. >> To quickly fix this (i was/am a bit in the rush), i added the bin >> directory for both the >> build-to-host cross-compiler and the build-to-target one to my PATH >> and correctly set the >> build-system-tuple as well as the host-system-tuple. > There are two ways you can handle this: > > 1- enter only the tuple- name of the two cross-compilers, and them > in the PATH, as you did, eg.: > CT_HOST_PREFIX="arm-unknown-linux-gnueabi-" > CT_TARGET_PREFIX="mips-unknwon-linux-gnu-" > PATH="/path/to/arm-compiler/bin:/path/to/mips-compiler:${PATH}" > > 2- enter the fully qualified path to your compiler, so there is no need > to change your PATH, eg.: > CT_HOST_PREFIX="/path/to/arm-compiler/bin/arm-unknown-linux-gnueabi-" > CT_TARGET_PREFIX="/path/to/mips-compiler/mips-unknwon-linux-gnu-" > >> So you need to have these 2 cross-compilers built before starting the canadian. > Yes, currently the canadian infrastrucutre requires that two cross-compiler > pre-exist: > - the build->host cross-compiler, to be able to build the tools that will > ultimately run on host (gcc, binutils...) > - the build->target cross-compiler, to be able to build the libraries and > tools that will ultimately run on the target (glibc, libgcc...) > >> Have a look at: http://sourceware.org/ml/crossgcc/2011-03/msg00069.html > This thread is about the on-going revamp of the canadian infrastructure (yes, > it's been on-going for that long, even much longer...). It does not really > apply in this case... > > Regards, > Yann E. MORIN. > -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-07 19:01 Tobias Arp 2012-03-07 19:37 ` Samuel Martin @ 2012-03-08 7:49 ` Per Arnold Blaasmo 2012-03-08 9:47 ` Thomas Petazzoni 2 siblings, 0 replies; 10+ messages in thread From: Per Arnold Blaasmo @ 2012-03-08 7:49 UTC (permalink / raw) To: crossgcc [-- Attachment #1: Type: text/plain, Size: 1293 bytes --] On 07. mars 2012 20:01, Tobias Arp wrote: > Hi, > > i try to do a canadian build with crosstool-ng 1.14.1. > > Build=i686-pc-linux-gnu > > Host=i586-pc-linux-gnu > > Target=arm > > > What do i have to put in *** Build system *** -> Tuple > and in *** Host system *** Tuple. > > When i add this for the build system: i686-pc-linux-gnu > and this for the host: i586-pc-linux-gnu > > I get this error: > > [INFO ] Performing some trivial sanity checks > [INFO ] Build started 20120307.200018 > [INFO ] Building environment variables > [WARN ] Directory '/home/tobias/src' does not exist. > [WARN ] Will not save downloaded tarballs to local storage. > [EXTRA] Preparing working directories > [ERROR] Missing: 'i586-pc-linux-gnu-ar' or 'i586-pc-linux-gnu-ar' or 'ar' : either needed! > [00:01] / make: *** [build] Fehler 1 > > > > Best regards > > Tobias > Here is a config file I use to build with canadian cross: Build: x86_64-pc-linux-gnu Host: i686-pc-linux-gnu Target: arm-none-eabi I works for me. You have to build the arm-non-eabi compiler for x86_64-pc-linux-gnu first and put it in ${CT_TOP_DIR}/x-tools/x86_64/ I have a Jenkins build job that uses an ant script to first build native arm-none-eabi for x86_64, then canadian crosss for i686 and mingw32. Per A. [-- Attachment #2: config.x86-pc-linux_arm-none-eabi --] [-- Type: text/plain, Size: 9243 bytes --] # # Automatically generated make config: don't edit # crosstool-NG 1.14.0 Configuration # Wed Feb 1 14:32:17 2012 # CT_CONFIGURE_has_xz=y CT_CONFIGURE_has_cvs=y CT_CONFIGURE_has_svn=y CT_MODULES=y # # Paths and misc options # # # crosstool-NG behavior # # CT_OBSOLETE is not set CT_EXPERIMENTAL=y # CT_DEBUG_CT is not set # # Paths # CT_LOCAL_TARBALLS_DIR="${HOME}/lib" CT_WORK_DIR="${CT_TOP_DIR}/.build" CT_PREFIX_DIR="${HOME}/x-tools/x86/${CT_TARGET}" CT_INSTALL_DIR="${CT_PREFIX_DIR}" CT_RM_RF_PREFIX_DIR=y CT_REMOVE_DOCS=y # CT_INSTALL_DIR_RO is not set CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES=y # # Downloading # CT_FORBID_DOWNLOAD=y # CT_FORCE_DOWNLOAD is not set # CT_CONNECT_TIMEOUT=10 # CT_ONLY_DOWNLOAD is not set # CT_USE_MIRROR is not set # # Extracting # # CT_FORCE_EXTRACT is not set CT_OVERIDE_CONFIG_GUESS_SUB=y # CT_ONLY_EXTRACT is not set CT_PATCH_BUNDLED=y # CT_PATCH_LOCAL is not set # CT_PATCH_BUNDLED_LOCAL is not set # CT_PATCH_LOCAL_BUNDLED is not set # CT_PATCH_BUNDLED_FALLBACK_LOCAL is not set # CT_PATCH_LOCAL_FALLBACK_BUNDLED is not set # CT_PATCH_NONE is not set CT_PATCH_ORDER="bundled" # # Build behavior # CT_PARALLEL_JOBS=0 CT_LOAD=0 CT_USE_PIPES=y CT_EXTRA_FLAGS_FOR_HOST="-fno-stack-protector -U_FORTIFY_SOURCE --sysroot=${CT_TOP_DIR}/i686-pc-linux-gnu/i686-pc-linux-gnu/sysroot" # CT_CONFIG_SHELL_SH is not set # CT_CONFIG_SHELL_ASH is not set CT_CONFIG_SHELL_BASH=y # CT_CONFIG_SHELL_CUSTOM is not set CT_CONFIG_SHELL="${bash}" # # Logging # # CT_LOG_ERROR is not set # CT_LOG_WARN is not set # CT_LOG_INFO is not set CT_LOG_EXTRA=y # CT_LOG_ALL is not set # CT_LOG_DEBUG is not set CT_LOG_LEVEL_MAX="EXTRA" # CT_LOG_SEE_TOOLS_WARN is not set # CT_LOG_PROGRESS_BAR=y CT_LOG_TO_FILE=y CT_LOG_FILE_COMPRESS=y # # Target options # CT_ARCH="arm" CT_ARCH_SUPPORTS_BOTH_MMU=y CT_ARCH_SUPPORTS_BOTH_ENDIAN=y CT_ARCH_SUPPORTS_32=y CT_ARCH_SUPPORT_ARCH=y CT_ARCH_SUPPORT_CPU=y CT_ARCH_SUPPORT_TUNE=y CT_ARCH_SUPPORT_FPU=y CT_ARCH_DEFAULT_HAS_MMU=y CT_ARCH_DEFAULT_LE=y CT_ARCH_DEFAULT_32=y CT_ARCH_ARCH="armv7-m" CT_ARCH_CPU="" CT_ARCH_TUNE="cortex-m3" CT_ARCH_FPU="" # CT_ARCH_BE is not set CT_ARCH_LE=y CT_ARCH_32=y CT_ARCH_BITNESS=32 CT_ARCH_FLOAT_HW=y # CT_ARCH_FLOAT_SW is not set CT_TARGET_CFLAGS="" CT_TARGET_LDFLAGS="" CT_ARCH_arm=y # CT_ARCH_x86 is not set # CT_ARCH_sh is not set # CT_ARCH_avr32 is not set # CT_ARCH_mips is not set # CT_ARCH_sparc is not set # CT_ARCH_powerpc is not set # CT_ARCH_s390 is not set # CT_ARCH_m68k is not set # CT_ARCH_alpha is not set # CT_ARCH_blackfin is not set CT_ARCH_arm_AVAILABLE=y CT_ARCH_x86_AVAILABLE=y CT_ARCH_sh_AVAILABLE=y CT_ARCH_avr32_AVAILABLE=y CT_ARCH_mips_AVAILABLE=y CT_ARCH_sparc_AVAILABLE=y CT_ARCH_powerpc_AVAILABLE=y CT_ARCH_s390_AVAILABLE=y CT_ARCH_m68k_AVAILABLE=y CT_ARCH_alpha_AVAILABLE=y CT_ARCH_blackfin_AVAILABLE=y # # Generic target options # CT_MULTILIB=y CT_ARCH_USE_MMU=y CT_ARCH_ENDIAN="little" # # Target optimisations # # CT_ARCH_FLOAT_SOFTFP is not set # CT_ARCH_FLOAT="soft" # # arm other options # CT_ARCH_ARM_MODE="thumb" # CT_ARCH_ARM_MODE_ARM is not set CT_ARCH_ARM_MODE_THUMB=y CT_ARCH_ARM_INTERWORKING=y CT_ARCH_ARM_EABI=y # # Toolchain options # # # General toolchain options # CT_FORCE_SYSROOT=y CT_USE_SYSROOT=y CT_SYSROOT_NAME="sysroot" CT_SYSROOT_DIR_PREFIX="" CT_WANTS_STATIC_LINK=y CT_STATIC_TOOLCHAIN=y CT_TOOLCHAIN_PKGVERSION="Atmel build: ${BUILD_NUMBER}" CT_TOOLCHAIN_BUGURL="http://www.atmel.com" # # Tuple completion and aliasing # CT_TARGET_VENDOR="none" CT_TARGET_ALIAS_SED_EXPR="" CT_TARGET_ALIAS="" # # Toolchain type # # CT_NATIVE is not set # CT_CROSS is not set # CT_CROSS_NATIVE is not set CT_CANADIAN=y CT_TOOLCHAIN_TYPE="canadian" # # Build system # CT_BUILD="" CT_BUILD_PREFIX="" CT_BUILD_SUFFIX="" # # Host system # CT_HOST="i686-pc-linux-gnu" CT_HOST_PREFIX="${CT_TOP_DIR}/i686-pc-linux-gnu/bin/i686-pc-linux-gnu-" CT_HOST_SUFFIX="" # # Target system # CT_TARGET_PREFIX="${CT_TOP_DIR}/x-tools/x86_64/arm-none-eabi/bin/arm-none-eabi-" CT_TARGET_SUFFIX="" # # Operating System # CT_BARE_METAL=y CT_KERNEL="bare-metal" CT_KERNEL_bare_metal=y # CT_KERNEL_linux is not set CT_KERNEL_mingw32_AVAILABLE=y CT_KERNEL_bare_metal_AVAILABLE=y CT_KERNEL_linux_AVAILABLE=y # # Common kernel options # # # Binary utilities # CT_ARCH_BINFMT_ELF=y # # GNU binutils # CT_BINUTILS_V_2_22=y # CT_BINUTILS_V_2_21_53 is not set # CT_BINUTILS_V_2_21_1a is not set # CT_BINUTILS_V_2_20_1a is not set # CT_BINUTILS_V_2_19_1a is not set # CT_BINUTILS_V_2_18a is not set # CT_BINUTILS_V_2_17a is not set # CT_BINUTILS_V_2_16_1a is not set CT_BINUTILS_VERSION="2.22" CT_BINUTILS_2_22_or_later=y CT_BINUTILS_2_21_or_later=y CT_BINUTILS_2_20_or_later=y CT_BINUTILS_2_19_or_later=y CT_BINUTILS_2_18_or_later=y CT_BINUTILS_HAS_GOLD=y CT_BINUTILS_GOLD_SUPPORTS_ARCH=y CT_BINUTILS_HAS_PLUGINS=y CT_BINUTILS_HAS_PKGVERSION_BUGURL=y CT_BINUTILS_LINKER_LD=y # CT_BINUTILS_LINKER_GOLD is not set # CT_BINUTILS_LINKER_LD_GOLD is not set # CT_BINUTILS_LINKER_GOLD_LD is not set CT_BINUTILS_LINKERS_LIST="ld" CT_BINUTILS_LINKER_DEFAULT="bfd" # CT_BINUTILS_PLUGINS is not set CT_BINUTILS_EXTRA_CONFIG_ARRAY="" # # C compiler # CT_CC="gcc" CT_CC_VERSION="4.6.2" CT_CC_gcc=y # CT_CC_GCC_SHOW_LINARO is not set CT_CC_V_4_6_2=y # CT_CC_V_4_6_1 is not set # CT_CC_V_4_6_0 is not set # CT_CC_V_4_5_3 is not set # CT_CC_V_4_5_2 is not set # CT_CC_V_4_5_1 is not set # CT_CC_V_4_5_0 is not set # CT_CC_V_4_4_6 is not set # CT_CC_V_4_4_5 is not set # CT_CC_V_4_4_4 is not set # CT_CC_V_4_4_3 is not set # CT_CC_V_4_4_2 is not set # CT_CC_V_4_4_1 is not set # CT_CC_V_4_4_0 is not set # CT_CC_V_4_3_6 is not set # CT_CC_V_4_3_5 is not set # CT_CC_V_4_3_4 is not set # CT_CC_V_4_3_3 is not set # CT_CC_V_4_3_2 is not set # CT_CC_V_4_3_1 is not set # CT_CC_V_4_2_4 is not set # CT_CC_V_4_2_3 is not set # CT_CC_V_4_2_2 is not set CT_CC_GCC_4_2_or_later=y CT_CC_GCC_4_3_or_later=y CT_CC_GCC_4_4_or_later=y CT_CC_GCC_4_5_or_later=y CT_CC_GCC_4_6=y CT_CC_GCC_4_6_or_later=y CT_CC_GCC_HAS_GRAPHITE=y CT_CC_GCC_HAS_LTO=y CT_CC_GCC_HAS_PKGVERSION_BUGURL=y CT_CC_GCC_HAS_BUILD_ID=y CT_CC_GCC_USE_GMP_MPFR=y #CT_CC_GCC_USE_PPL_CLOOG=y CT_CC_GCC_USE_MPC=y CT_CC_SUPPORT_CXX=y CT_CC_SUPPORT_FORTRAN=y CT_CC_SUPPORT_JAVA=y CT_CC_SUPPORT_ADA=y CT_CC_SUPPORT_OBJC=y CT_CC_SUPPORT_OBJCXX=y # # Additional supported languages: # CT_CC_LANG_CXX=y # # gcc other options # CT_CC_ENABLE_CXX_FLAGS="" CT_CC_CORE_EXTRA_CONFIG_ARRAY="--with-mode=thumb --disable-libstdcxx-pch" CT_CC_STATIC_LIBSTDCXX=y #CT_CC_GCC_SYSTEM_ZLIB=y # # Optimisation features # #CT_CC_GCC_USE_GRAPHITE=y CT_CC_GCC_USE_LTO=y # # Settings for libraries running on target # CT_CC_GCC_ENABLE_TARGET_OPTSPACE=y # CT_CC_GCC_LIBMUDFLAP is not set # CT_CC_GCC_LIBGOMP is not set # CT_CC_GCC_LIBSSP is not set # # Misc. obscure options. # CT_CC_GCC_DISABLE_PCH=y CT_CC_GCC_LDBL_128=m # CT_CC_GCC_BUILD_ID is not set # # C-library # CT_LIBC="newlib" CT_LIBC_VERSION="1.19.0" # CT_LIBC_none is not set CT_LIBC_newlib=y CT_LIBC_none_AVAILABLE=y CT_LIBC_mingw_AVAILABLE=y CT_LIBC_glibc_AVAILABLE=y CT_LIBC_newlib_AVAILABLE=y CT_LIBC_NEWLIB_V_1_19_0=y # CT_LIBC_NEWLIB_V_1_18_0 is not set # CT_LIBC_NEWLIB_V_1_17_0 is not set # CT_LIBC_NEWLIB_CVS is not set # # Architecture specific options # CT_LIBC_uClibc_AVAILABLE=y CT_LIBC_eglibc_AVAILABLE=y CT_LIBC_SUPPORT_THREADS_NONE=y CT_THREADS="none" # # Common C library options # CT_THREADS_NONE=y # # newlib other options # # CT_LIBC_NEWLIB_IO_C99FMT is not set CT_LIBC_NEWLIB_IO_LL=y # CT_LIBC_NEWLIB_IO_FLOAT is not set CT_LIBC_NEWLIB_DISABLE_SUPPLIED_SYSCALLS=y CT_LIBC_NEWLIB_ENABLE_TARGET_OPTSPACE=y CT_LIBC_NEWLIB_EXTRA_CONFIG_ARRAY="--enable-newlib-register-fini" # # Debug facilities # # CT_DEBUG_gdb is not set # CT_DEBUG_ltrace is not set # CT_DEBUG_duma is not set # CT_DEBUG_dmalloc is not set # CT_DEBUG_strace is not set # # Companion libraries # CT_COMPLIBS_NEEDED=y CT_GMP_NEEDED=y CT_MPFR_NEEDED=y #CT_PPL_NEEDED=y # CT_CLOOG_NEEDED=y CT_MPC_NEEDED=y CT_COMPLIBS=y CT_GMP=y CT_MPFR=y #CT_PPL=y # CT_CLOOG=y CT_MPC=y CT_GMP_V_5_0_2=y # CT_GMP_V_5_0_1 is not set # CT_GMP_V_4_3_2 is not set # CT_GMP_V_4_3_1 is not set # CT_GMP_V_4_3_0 is not set CT_GMP_VERSION="5.0.2" # CT_MPFR_V_3_1_0 is not set CT_MPFR_V_3_0_1=y # CT_MPFR_V_3_0_0 is not set # CT_MPFR_V_2_4_2 is not set # CT_MPFR_V_2_4_1 is not set # CT_MPFR_V_2_4_0 is not set CT_MPFR_VERSION="3.0.1" #CT_PPL_V_0_11_2=y # CT_PPL_V_0_11_1 is not set # CT_PPL_V_0_11 is not set # CT_PPL_V_0_10_2 is not set #CT_PPL_VERSION="0.11.2" #CT_PPL_0_11=y #CT_PPL_NEEDS_LIBPWL=y #CT_CLOOG_V_0_15_11=y # CT_CLOOG_V_0_15_10 is not set # CT_CLOOG_V_0_15_9 is not set # CT_CLOOG_V_0_15_8 is not set # CT_CLOOG_V_0_15_7 is not set # CT_CLOOG_V_0_15_6 is not set #CT_CLOOG_VERSION="0.15.11" #CT_CLOOG_0_15_1x=y #CT_CLOOG_NEEDS_AUTORECONF=y CT_MPC_V_0_9=y # CT_MPC_V_0_8_2 is not set # CT_MPC_V_0_8_1 is not set # CT_MPC_V_0_7 is not set CT_MPC_VERSION="0.9" # # Companion libraries common options # # CT_COMPLIBS_CHECK is not set # # Companion tools # # # READ HELP before you say 'Y' below !!! # CT_COMP_TOOLS=y CT_COMP_TOOLS_make=y CT_COMP_TOOLS_m4=y CT_COMP_TOOLS_autoconf=y CT_COMP_TOOLS_automake=y CT_COMP_TOOLS_libtool=y # # Test suite # # CT_TEST_SUITE_GCC is not set [-- Attachment #3: Type: text/plain, Size: 71 bytes --] -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-07 19:01 Tobias Arp 2012-03-07 19:37 ` Samuel Martin 2012-03-08 7:49 ` Per Arnold Blaasmo @ 2012-03-08 9:47 ` Thomas Petazzoni 2012-03-08 18:26 ` Yann E. MORIN 2 siblings, 1 reply; 10+ messages in thread From: Thomas Petazzoni @ 2012-03-08 9:47 UTC (permalink / raw) To: crossgcc Le Wed, 7 Mar 2012 20:01:04 +0100 (CET), "Tobias Arp" <tobiasarp@web.de> a écrit : > Build=i686-pc-linux-gnu > Host=i586-pc-linux-gnu > Target=arm Just curious: do you really need to use the canadian mechanism to build such a toolchain? If it's just a matter of having i586 binaries instead of i686 binaries, isn't it simpler to just pass -march=i586 to the CFLAGS used when building the host utilities, and therefore do a normal cross-compiler? Or maybe I'm missing something? Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-08 9:47 ` Thomas Petazzoni @ 2012-03-08 18:26 ` Yann E. MORIN 2012-03-08 18:52 ` Tobias Arp 0 siblings, 1 reply; 10+ messages in thread From: Yann E. MORIN @ 2012-03-08 18:26 UTC (permalink / raw) To: crossgcc; +Cc: Thomas Petazzoni, Tobias Arp Thomas, Tobias, All On Thursday 08 March 2012 10:47:26 Thomas Petazzoni wrote: > Le Wed, 7 Mar 2012 20:01:04 +0100 (CET), > "Tobias Arp" <tobiasarp@web.de> a écrit : > > > Build=i686-pc-linux-gnu > > Host=i586-pc-linux-gnu > > Target=arm > > Just curious: do you really need to use the canadian mechanism to build > such a toolchain? If it's just a matter of having i586 binaries instead > of i686 binaries, isn't it simpler to just pass -march=i586 to the > CFLAGS used when building the host utilities, and therefore do a normal > cross-compiler? Or maybe I'm missing something? It might probably be a completely different system (eg a different libc version, or even a different libc, and so on...). A tuple is not really enough to differentiate any two systems. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: canadian build 2012-03-08 18:26 ` Yann E. MORIN @ 2012-03-08 18:52 ` Tobias Arp 0 siblings, 0 replies; 10+ messages in thread From: Tobias Arp @ 2012-03-08 18:52 UTC (permalink / raw) To: Yann E. MORIN; +Cc: crossgcc, Thomas Petazzoni Thomas, Yann, All, > Thomas, Tobias, All > > On Thursday 08 March 2012 10:47:26 Thomas Petazzoni wrote: >> Le Wed, 7 Mar 2012 20:01:04 +0100 (CET), >> "Tobias Arp"<tobiasarp@web.de> a écrit : >> >>> Build=i686-pc-linux-gnu >>> Host=i586-pc-linux-gnu >>> Target=arm >> Just curious: do you really need to use the canadian mechanism to build >> such a toolchain? If it's just a matter of having i586 binaries instead >> of i686 binaries, isn't it simpler to just pass -march=i586 to the >> CFLAGS used when building the host utilities, and therefore do a normal >> cross-compiler? Or maybe I'm missing something? You are right, but Yann got the point. Its a different system. > It might probably be a completely different system (eg a different libc > version, or even a different libc, and so on...). A tuple is not really > enough to differentiate any two systems. > > Regards, > Yann E. MORIN. > But we can close this thread with your help i found my problem... it was a typo in my script... Thanks to all who helped me. Tobias -- For unsubscribe information see http://sourceware.org/lists.html#faq ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2015-10-22 2:41 UTC | newest] Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-10-22 2:39 canadian build Randy Yates 2015-10-22 2:41 ` Randy Yates -- strict thread matches above, loose matches on Subject: below -- 2012-03-07 19:01 Tobias Arp 2012-03-07 19:37 ` Samuel Martin 2012-03-07 20:17 ` Yann E. MORIN 2012-03-08 7:48 ` Tobias Arp 2012-03-08 7:49 ` Per Arnold Blaasmo 2012-03-08 9:47 ` Thomas Petazzoni 2012-03-08 18:26 ` Yann E. MORIN 2012-03-08 18:52 ` Tobias Arp
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).