search for: cc_for_build

...oftware; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.' + help=' Try `config.guess --help'\'' for more information.' + test 0 -gt 0 + test 0 '!=' 0 + trap 'exit 1' 1 2 15 + set_cc_for_build=' trap "exitcode=\$?; (rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null) && exit \$exitcode" 0 ; trap "rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null; exit 1" 1 2 13 15 ; : ${TMPDIR=/tmp} ; { tmp=`(umask 077 && mktemp -d "$TMP...

...ditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE.' > + help=' > Try `config.guess --help'\'' for more information.' > + test 0 -gt 0 > + test 0 '!=' 0 > + trap 'exit 1' 1 2 15 > + set_cc_for_build=' > trap "exitcode=\$?; (rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp > 2>/dev/null) && exit \$exitcode" 0 ; > trap "rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null; exit 1" 1 > 2 13 15 ; > : ${TMPDIR=/tmp} ; > { tmp=`(umask 077 &a...

...ditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE.' > + help=' > Try `config.guess --help'\'' for more information.' > + test 0 -gt 0 > + test 0 '!=' 0 > + trap 'exit 1' 1 2 15 > + set_cc_for_build=' > trap "exitcode=\$?; (rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp > 2>/dev/null) && exit \$exitcode" 0 ; > trap "rm -f \$tmpfiles 2>/dev/null; rmdir \$tmp 2>/dev/null; exit 1" 1 > 2 13 15 ; > : ${TMPDIR=/tmp} ; > { tmp=`(umask 077 &a...

Ever since 2.26 I haven't been able to upgrade. In fact the install locks up my server. I get into and infinite recursive loop where the config-guess program calls itself until the server locks up from overload. I'm running Centos 6 under OpenVZ. What am I missing? I think there's a serious bug. 31233 pts/3 S 0:00 /bin/sh ./config.guess 31235 pts/3 S 0:00 \_

Hi together, this is the second version of my cross-compilation patch serie. I'm sending it in the hope to get an honest review, and possibly see the patches integrated upstream. Those patches allow to build syslinux using a toolchain different from the host one by explicitely using the host toolchain for the utilities that are required at build-time / on the build machine. I am using the

...> Duncan, Yes, the result from "./TargetInfo -p" is incorrect under darwin10... x86 In FSF config.guess, we had to add... *:Darwin:*:*) UNAME_PROCESSOR=`uname -p` || UNAME_PROCESSOR=unknown case $UNAME_PROCESSOR in i386) eval $set_cc_for_build if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \ (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \ grep IS_64BIT_ARCH &...

Hi All, I recently ran into an issue that was posted several years back on LLVMdev [1]. A brief recap of the problem is that when cross-compiling LLVM itself the configure/make scripts get confused when creating the needed build host tools. For example, building and configuring like: CC_FOR_BUILD='i686-pc-linux-gnu-gcc' CXX_FOR_BUILD='i686-pc-linux-gnu-g++' CXX='i686-mingw32-g++' CC='i686-mingw32-gcc' LD='i686-mingw32-ld' /scratch /meadori/llvm-trunk/src/trunk/configure --host=i686-mingw32 CC_FOR_BUILD='i686-pc-linux-gnu-gcc' CXX_FOR_BU...

Hi Jack, > The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn > (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the > build fails as... what does the command ./TargetInfo -p return (the TargetInfo program is created during the dragonegg build). Some of your errors are consistent with this program failing to run.

...getInfo -p" is incorrect under darwin10... > > x86 > > In FSF config.guess, we had to add... > > *:Darwin:*:*) > UNAME_PROCESSOR=`uname -p` || UNAME_PROCESSOR=unknown > case $UNAME_PROCESSOR in > i386) > eval $set_cc_for_build > if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then > if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \ > (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \ >...

.... ---------------------------- Now, xgcc is from llvm-gcc, so I'm not sure if my locally installed GCC compiler is at fault, which is "gcc (GCC) 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)" I'm now trying to compile llvm-gcc with ---------------------------- make CC=gcc-4.2 CC_FOR_BUILD=gcc-4.2 CXX=g++-4.2 CXX_FOR_BUILD=g++-4.2 ----------------------------

...QAContact: rsync-qa@samba.org The makefiles try to build the "mkrounding" tool with the "host" compiler; however, this file is being executed later in the build, so it has to be compiled with the "build" compiler. Usually, autotoolized Makefiles solve this by using CC_FOR_BUILD and the related CFLAGS_FOR_BUILD and LDFLAGS_FOR_BUILD. Error message, taken during a build for ARM here: ----------8<----------8<---------- arm-v4t-linux-gnueabi-gcc -std=gnu99 -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -L/some/path/sysroot/arm-v4t-linux-gnueabi/lib -L/some/path/sysroot/arm-...

Hi there, I've had issue with the integration of syslinux into the buildroot project [0]. After some research, it turned out that we were wrongly using the host toolchain instead of the target toolchain to build syslinux. This gave us bigger issues (for instance) when trying to link syslinux with gnu-efi, that was built using the target toolchain. The first one forces ld to output i386

...(-) diff --git a/utils/Makefile b/utils/Makefile index dfe6259..f31f117 100644 --- a/utils/Makefile +++ b/utils/Makefile @@ -17,8 +17,9 @@ VPATH = $(SRC) include $(MAKEDIR)/syslinux.mk -CFLAGS = $(GCCWARN) -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I$(SRC) -LDFLAGS = -O2 +CC = $(CC_FOR_BUILD) +CFLAGS = $(CFLAGS_FOR_BUILD) $(GCCWARN) -Os -fomit-frame-pointer -D_FILE_OFFSET_BITS=64 -I$(SRC) +LDFLAGS = $(LDFLAGS_FOR_BUILD) -O2 C_TARGETS = isohybrid gethostip memdiskfind SCRIPT_TARGETS = mkdiskimage -- 2.1.4

Hello, I see that in 6.04-pre3 there is some support for host and target gcc. However, build always fails when using a cross-compiler: [ 89s] + make CC=x86_64-suse-linux-gcc CC_FOR_BUILD=gcc ... [ 401s] objcopy --strip-debug --strip-unneeded libutil.elf libutil.c32 [ 401s] x86_64-suse-linux-gcc -I/home/abuild/rpmbuild/BUILD/syslinux-6.04~pre3+git3.05ac953c/com32/libutil/include -W -Wall -O -g -D_GNU_SOURCE -c -o ansiline.lo /home/abuild/rpmbuild/BUILD/syslinux-6.04~pre3+git3.05ac...

...Rework code to choose local connection types and fallback to others Sun bug #6739431: double free in _X11TransConnectDisplay() Chris Ball (1): Remove configure check for xcb-xlib. Daniel Stone (2): gitignore: Update with loads more bits from server configure.ac: Fix CC_FOR_BUILD logic error James Cloos (9): Fix commit 21e464ec682ab23ba20ddf6bd72c6db214cfbe01 Add <Multi_key> <cedilla> Compose tuples Work on making the en_US and pt_BR UTF-8 Compose as similar as possible. Add more <Multi_key> <cedilla> Compose tuples nls...

The new dragonegg 2.9 sources fail to build against either FSF gcc 4.5.2 or 4.5.3svn (with the i386_static.diff patch applied) on x86_64-apple-darwin10. In both cases, the build fails as... GCC=/sw/lib/gcc4.5/bin/gcc-4 LLVM_CONFIG=/sw/bin/llvm-config make CPPFLAGS="-DENABLE_LTO -I/sw/include" Compiling utils/TargetInfo.cpp <command-line>: warning: "__STDC_LIMIT_MACROS"

...se variables are not present. As it turned out, overriding the CC make variable is error-prone, so in the meantime, I have a new version of that patch that does it differently. I will send it once we agree on the need for a fix in that direction. I have a third patch that builds prepcore using the CC_FOR_BUILD compiler as well. That one was forgotten in my first serie. If you look inside the file ``mk/build.mk``, there is already a comment that mention that the distinction between the build toolchain and the host toolchain should be made. Can we at least agree that some step forward have to be made ther...

...llvm/build/libiberty' make[1]: Entering directory `/tmp/llvm3/llvm/build/intl' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/tmp/llvm3/llvm/build/intl' make[1]: Entering directory `/tmp/llvm3/llvm/build/zlib' : make ; exec true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-O2" "CXXFLAGS=-O2" "CFLAGS_FOR_BUILD=" "CFLAGS_FO R_TARGET=-O2 -O2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/us r/bin/install -c" "INSTALL_SCRIPT=/usr/bin/i...

hpa wrote: > On July 7, 2019 8:37:10 AM PDT, Sebastian Herbszt <herbszt at gmx.de> > wrote: > >Gene, > > > >it looks like the syslinux master branch is broken since February > >[1]. Peter created the wip.makefixes branch but I wasn't able to get > >it working (yet) and it lacks activity since March. > > > >I think it might be time to revert

...> make[1]: Entering directory `/tmp/llvm3/llvm/build/intl' > make[1]: Nothing to be done for `all'. > make[1]: Leaving directory `/tmp/llvm3/llvm/build/intl' > make[1]: Entering directory `/tmp/llvm3/llvm/build/zlib' > : make ; exec true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-O2" "CXXFLAGS=-O2" "CFLAGS_FOR_BUILD=" "CFLAGS_FO > R_TARGET=-O2 -O2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/us > r/bin/install -c" "INSTALL_SCRIPT=...