similar to: Building an LLVM/CLANG cross compiler for legacy GCC toolchain

I am cross-compiling rsync 2.6.2 on Linux i386 for Linux ARM. I pass the following to configure: LDSHARED=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gcc CXX=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-g++ CC=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-gcc AR=~/buildroot/build_arm_nofpu/staging_dir/bin/arm-linux-uclibc-ar

Hi, this commit https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: make[3]: Entering directory '/home/bernd/buildroot/br4/output/build/dovecot-2.2.33.2/src/lib-test' /bin/bash ../../libtool --tag=CC --mode=compile

Hi, i tried to compile dovecot 2.2.0 and i end up with this error: make[6]: Entering directory `/mnt/data/Develop/Openwrt/trunk_git/build_dir/target-mips_r2_uClibc-0.9.33.2/dovecot-2.2.0/src/util' /bin/sh ../../libtool --tag=CC --mode=link mips-openwrt-linux-uclibc-gcc -std=gnu99 -Os -pipe -mips32r2 -mtune=mips32r2 -fno-caller-saves -mno-branch-likely -fhonour-copts

Howdy. I'm one of the maintainers of Astlinux (www.astlinux.org). We're updating the kernel from 2.6.20, to 2.6.25 (.19), and as such, some packages that previously compiled stopped doing so. We also went from syslinux-3.63 to syslinux-3.72, hoping that a newer version would be more amenable to a more recent kernel. No joy. We're cross-compiling on FC8 (updated) on an i386

On Mon, Nov 13, 2017 at 20:07:00 +0100, Bernd Kuhls wrote: > Hi, > > this commit > https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 > > added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: Hrm... ok. It'll be probably faster for you to try a test build instead of me setting up buildroot... What happens if in

Hi, I want to explorer affection of compiler on low power. For the project background, I tend to process this work via LLVM, rather than GCC. And the Target is ARM. For this purpose, clang(3.2) + arm-gcc + simplescalar-arm(and panalyzer) seems to be a good choice. But I encounter several problems in the processing of setup the environment. ---------------------------------- 1. Firstly, arm

Hi I am trying to build Xenclient and while it builds gcc, it returns following error. /home/vinxen/xenclient/build/toolchain_build_i686/gcc-4.2.4-initial/./gc c/xgcc -B/home/vinxen/xenclient/build/toolchain_build_i686/gcc-4.2.4-initial/./ gcc/ -B/home/vinxen/xenclient/build/build_i686/staging_dir/usr/i686-linux-ucl ibc/bin/

Hi, I have cross compiled samba 3.3.8 for arm, which succeeded. However, the size of the resulting binaries is large (few MB's per binary) so the total installation of samba sums to over 50 megabytes, after stripping the binaries. For example, with samba 2.0.10, the size of smbd was 281 KB. With samba 3.3.8 that is 5.2 MB. Same goes for the other binaries. It looks as if there is a chunk of

http://bugzilla.netfilter.org/show_bug.cgi?id=569 Summary: in6addr_any undeclared Product: iptables Version: CVS (please indicate timestamp) Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: unknown AssignedTo: laforge at netfilter.org ReportedBy:

On Mon, Jan 7, 2019 at 5:50 AM Clement Courbet <courbet at google.com> wrote: > On Fri, Jan 4, 2019 at 12:34 PM James Y Knight via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> This seems a somewhat odd and overcomplicated way to go about this. >>> >>> Given that bcmp was required in POSIX until relatively recently, I will

Jeremy Allison <jra <at> samba.org> writes: > > On Sat, Mar 12, 2016 at 11:16:36AM +0000, Andy Walsh wrote: > > > > Also keep in mind that samba3.6 was successfully adopted on any device that > > had a usb2.0 port in the past. So slapping a usbstick/sdcard/hdd on a cheap > > router is already a common scenario. > > Yes, and I'd like to help

Hello, In my reading over the last couple of days, I have read that in order for klee to work with "native" Linux programs, I need to install the uClibc posix support for klee. I am not finding the uClibc source in the llvm svn repository anywhere. Is this still necessary for testing native Linux applications, and if so, where do I get the uClibc source to compile? Thanks in

Hi, I have used bridge-utils 0.9.6 so far in a kernel 2.4.26, uClibc and ppc environment. When I use version 1.0.3 I have the problem that I do not see the brige with the 'brctl show' command if it is not fully set up. It was working with 0.9.6. I tracked the problem down to an 'incompatibility' in bridge/uClibc/kernel. 0.9.6 uses its own if_indextoname function which uses the

On Sat, Mar 12, 2016 at 05:19:13PM +0000, Andy Walsh wrote: > Jeremy Allison <jra <at> samba.org> writes: > > > > > On Sat, Mar 12, 2016 at 11:16:36AM +0000, Andy Walsh wrote: > > > > > > Also keep in mind that samba3.6 was successfully adopted on any device that > > > had a usb2.0 port in the past. So slapping a usbstick/sdcard/hdd on a

Hello. I managed to setup a cross compiler on my Gentoo system to compile for arm platform. I installed all nessecary tools and libs in /usr/arm-unknown-linux-uclibc/ like openssl lzo and so on over the cross emerge package manager. But what command is nessecary to configure tinc to run on arm? I used: ./configure --host=arm-unknown-linux-uclibc

On 9/12/07, Chris Lattner <sabre at nondot.org> wrote: > > On Wed, 12 Sep 2007, Dound wrote: > > I am trying compile a libc with llvm (currently uclibc). I am able to > > compile uclibc by changing the Rules.mak to use llvm-gcc, llvm-ar, > llvm-ad, > > and not using strip. (I also use the --emit-llvm flag for > llvm-gcc). When > > I run llvm-nm on

Skipped content of type multipart/alternative-------------- next part -------------- pending configuration tag "CXX" to libtool checking for ld used by /home/jessy/process_ctrl_7_21/toolChains/cross_arm/bin/arm-linux-uclibc-g++... /home/jessy/proce ss_ctrl_7_21/toolChains/cross_arm/bin/arm-linux-uclibc-ld checking if the linker

On Wed, 12 Sep 2007, Dound wrote: > I am trying compile a libc with llvm (currently uclibc). I am able to > compile uclibc by changing the Rules.mak to use llvm-gcc, llvm-ar, llvm-ad, > and not using strip. (I also use the --emit-llvm flag for llvm-gcc). When > I run llvm-nm on libc.a (or try to use libc.a) I run into problems. For > example, strlen is not defined -- llvm-nm

Hello! This is my first time trying to run dovecot so maybe I've overlooked something, but I'm having a hard time running dovecot. First of all, it's worth noting that I'm trying to run dovecot on an embedded platform: the target architecture is mipsel; I have patches for the 2.4.18 kernel with special support for the board so I'm still using the 2.4.18 kernel. My C library

I am trying compile a libc with llvm (currently uclibc). I am able to compile uclibc by changing the Rules.mak to use llvm-gcc, llvm-ar, llvm-ad, and not using strip. (I also use the --emit-llvm flag for llvm-gcc). When I run llvm-nm on libc.a (or try to use libc.a) I run into problems. For example, strlen is not defined -- llvm-nm shows that strlen.os has __GI_strlen while if I compile with