similar to: DO NOT REPLY [Bug 5170] New: Cross compilation does not work

Hi. The small patch below fixes the building of 'mkrounding.o' when the build directory is outside the source directory. Art Haas Index: Makefile.in =================================================================== RCS file: /cvsroot/rsync/Makefile.in,v retrieving revision 1.128 diff -u -r1.128 Makefile.in --- Makefile.in 17 Dec 2006 00:40:18 -0000 1.128 +++ Makefile.in 27 Dec 2006

https://bugzilla.samba.org/show_bug.cgi?id=4981 Summary: iconv confusion Product: rsync Version: 3.0.0 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: joe07734@gmail.com QAContact:

https://bugzilla.samba.org/show_bug.cgi?id=5022 Summary: FreeBSD 4.11 - Compilation Fails - uidlist.c - gcc2 / gcc3 Product: rsync Version: 3.0.0 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Any concerns with the compiler warning on flist.c on a ia64 system running SLES10SP1? ~/rsync-3.0.0pre7> make gcc -std=gnu99 -g -O2 -DHAVE_CONFIG_H -Wall -W -o mkrounding -I. ./ mkrounding.c ./mkrounding >rounding.h Rounding file_extras in multiples of 2 (EXTRA_LEN=4, FILE_STRUCT_LEN=24) gcc -std=gnu99 -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c flist.c -o flist.o /tmp/ccqjJwNs.s:

with the recent move of the includes from linux' include/asm-$ARCH to arch/$ARCH/asm, klibc fails to compile, because the in-linux-header files include from asm/, but this is not in the header search path. e.g. against linux-2.6.27 arm: arm-iwmmx-linux-gnueabi-gcc -Wp,-MD,usr/klibc/.vsnprintf.o.d -nostdinc -iwithprefix include -Iusr/include/arch/arm -Iusr/include/bits32

Hi anyone. When I run make trying to compile Dovecot for a network attached storage box and it fails. I have used two variants of configuration: The first ./configure i_cv_epoll_works=no i_cv_inotify_works=no i_cv_posix_fallocate_works=no i_cv_signed_size_t=no i_cv_gmtime_max_time_t=32 i_cv_signed_time_t=yes i_cv_mmap_plays_with_write=yes i_cv_fd_passing=yes i_cv_c99_vsnprintf=yes

Hi,    I use the crosstool build script to build a crosscompiler for ARM. I get the following error when compilng "helloworld" program:   llvm-gcc hello.c -o hello   as: unrecognized option `-meabi=4'   I know that the reason is not to get proper cross assembler. It tries to use the native assembler but I am unable to fix the problem. I use llvm-gcc -### hello.c -o hello and see

Hi,    I use the crosstool build script to build a crosscompiler for ARM. I get the following error when compilng "helloworld" program:   llvm-gcc hello.c -o hello   as: unrecognized option `-meabi=4'   I know that the reason is not to get proper cross assembler. It tries to use the native assembler but I am unable to fix the problem. I use llvm-gcc -### hello.c -o hello and see

Hi Journeyer First, thank you so much for your updates on your experiments. I am currently following your steps but have found myself stuck with the following error: /usr/lib/gcc/arm-linux-gnueabi/4.6/../../../../arm-linux-gnueabi/bin/ld: this linker was not configured to use sysroots clang: error: linker command failed with exit code 1 (use -v to see invocation) I used the command string you

Hi Team, We need freeradius-server-3.0.21 to be cross compiled for armv7 based Marvell switch. Toolchain: armv7-marvell-linux-gnueabi-LE_i686_20160226 host : arm-none-linux-gnueabi CC : arm-marvell-linux-gnueabi-gcc For that talloc is dependent library. Trying to cross compile talloc-2.3.1 to for our architecture with below command. ./configure --disable-python --enable-gccdeps

Hello Anton, Thanks for replying. The message "as: unrecognized option `-mcpu=cortex-a8'" is the same message I get when I just enter: as -mcpu=cortex-a8 So I think I llvm-gcc is using the Linux i386 assembler to assemble ARM code. Not good. What assembler is it supposed to use? The one in CodeSourcery? > But how's assembler actually called? Just try to compile

Dear all, I am using initramfs and from the kernel document, I know klibc. So i decide to use it. We are working on marvell pxa310 (bought from Intel), and with the tools chain from marvell, I comple klibc as follows: klibc-1.5> ln -s /home/zjujoe/svn/mhlv_2.6/working/songlixin/20081007_kernel_tflashupdate/ linux klibc-1.5>cat 1.sh export KLIBCARCH=arm export

Hello, am I wrong or the ARM c++ exceptions handling does not work? See the difference between assembly generated by clang and gcc with the following test code: #include <stdio.h> #include <exception> # test.cpp int main() { try { throw 20; } catch (int e) { printf("Exception Nr %d occurred\n", e); } return 0; }

Hello, Thank you for your kind attention to my issue and your help. I changed the tool chain and tried again. And there is a little progress but still have some problem. Using --sysroot doesn't make clang use linker(ld) in the cross tool. Most important question is how I can make clang use cross tool linker. Let me show you my experiment and questions below. There are two questions. [Run]

Hello Misha, I used the snapshots for the latest stable version (70786), and I followed the instructions inside of README file (very clear!!!) However, when I ran the hello program, I get an unrecognized option message. Bellow are the details. ============================================ jcmartin78 at jcmartin78-laptop:~/LLVM/my-test$ llvmc hello.c as: unrecognized option '-meabi=4'

On Wed, Jul 18, 2012 at 4:31 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 15:24, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> I'm not sure how to interpret the above output, but I don't understand >> why if say -triple armv4t-none--gnueabi . > > Ok, we're getting there... ;) Glad you are confident.

2015-03-11 16:22 GMT-05:00 Richard Gorton < rcgorton at cognitive-electronics.com>: > I can confirm that musl builds and works correctly with clang/llvm. We > are using musl as a libc for our architecture. > It has a much smaller code footprint than newlib or glibc. > I successfully cross-compile the must-libc using clang, with the configuration: C=clang

Hi, I am trying to cross compile LLVM-3.0 for Arm target i.e. I would like to run the LLVM tools on ARM platform and generate the code for the ARM platform. I configured the build with ../src/configure --build=i686-pc-linux-gnu --host=arm-linux-gnueabi --target=arm-linux-gnueabi --enable-optimized=no --prefix=/home/user/Acads/Compiler/LLVM/llvm-3.0/bin --with-as=/usr/bin/arm-linux-gnueabi-as

Hi All, I have downloaded libogg-1.3.0 along with speex.But,during build speex is exiting with ogg.h missing.Any suggestions will be highly appreciated. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hello, I'm using gold linker now to see if there can be any performance gain. Also using latest gcc version (4.4.4) and latest binutils. But when I'm compiling llvm-gcc, I'm getting this error. /home/jal/llvm-gcc-4.2-2.7.source/host-i686-pc-linux-gnu/gcc/xgcc -B/home/jal/llvm-gcc-4.2-2.7.source/host-i686-pc-linux-gnu/gcc/ -B/usr/local/arm-v7a8-linux-gnueabi/bin/