similar to: Samba 4 cross-compile for ARM

Sandeep Patel wrote: > The Nokia N800 is an OMAP 2420 which is an ARM11. > > If you want an OMAP 3530 today, I think the cheapest route is the Beagleboard. Yeah, I see that now, about the N800. About the BeagleBoard, if you're going after an equivalent # of peripherals (screen and keyboard are things I wanted) then, really, I think that the Pandora is cheapest. I will say, without

The Nokia N800 is an OMAP 2420 which is an ARM11. If you want an OMAP 3530 today, I think the cheapest route is the Beagleboard. deep On Wed, May 20, 2009 at 3:13 PM, Chuck Robey <chuckr at telenix.org> wrote: > Bob Wilson wrote: >> On May 20, 2009, at 1:38 PM, Chuck Robey wrote: >>> Hmm.  Well, my motivation is that I recently bought a Pandora (it >>> has the

Hi, Over the past few months I've been developing a LLVM backend for TIs C64X family of DSPs. It can be found as a co-processor in a variety of OMAP-based devices such as gumstix, beagleboard and even Nokia's N900 phone. A project I'm working on [0] has had need to put code on it, and we wanted to avoid TIs proprietary compiler. The DSP itself is a VLIW machine, with 64 32-bit

Hi List, I need your help in samba4.4 cross compile for PowerPC. Im using samba-4.4.5. As suggested by some folks in below links I used cross answers method. http://lists.openembedded.org/pipermail/openembedded-devel/2015-November/104549.html https://git.busybox.net/buildroot/commit/?id=dee1cf0cdf9db351fd94ccd864e09b3f1ec122f9 Configure is no issues. The main issue is for asn1_compile and

Hi All, I've recently dusted off my cross-compiling hat and decided to add R to the OpenEmbedded build environment (this is used to build the OpenZaurus/Familiar distributions for the Zaurus/iPAQ amongst other things - I note there's also work underway to add the Psion 5mx etc. to OpenEmbedded). OpenEmbedded builds now use -soft-float which makes floating point operations something like

Type of tx_ready callback got changed to int to faciliate error condition, but the ARM serial drivers were not modified thus breaking the compilation. Reported-by: Julien Grall <julien.grall@linaro.org> Signed-off-by: Tomasz Wroblewski <tomasz.wroblewski@citrix.com> --- xen/drivers/char/exynos4210-uart.c | 2 +- xen/drivers/char/omap-uart.c | 2 +-

Duncan Sands skrev: > Hi Xerxes, > > >> 4. softfloat related errors >> http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/softenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ >> example: >> >> root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc >>

Bob Wilson wrote: > On May 20, 2009, at 1:38 PM, Chuck Robey wrote: >> Hmm. Well, my motivation is that I recently bought a Pandora (it >> has the >> Cortex-A8). It's not going to arrive here for a couple more months, >> I think. >> When it does finally arrive, I want to be able to immediately begin >> work on >> replacing the Linux that

Hello Evan and Robert I have been investigating the unexpected test failures from the ARM nightly builders in order to get a better picture why the ARM backend don't pass the whole testsuite: I have run the failing tests manually on my arm board and can now categorize most of the thirteen unexpected CodeGen failures in four categories: 1. llvm don't lower MVT::i64 properly on arm

Hello, I'm trying to maintain the recipes for cross-building klibc in OpenEmbedded. Now, I still have a couple of doubts about packaging: first one is about klcc, which we have to rename blah-blah-klcc and to install in our sysroot. This file contains the paths of the toolchain, so it is not suitable for deployment on target device and we split the recipe and call it klcc-cross. But I see

Hi Xerxes, > 4. softfloat related errors > http://labb.zafena.se/shark-testing/llvmARMCodeGenFailures200904/softenfloat_Do_not_know_how_to_soften_the_result_of_this_operator/ > example: > > root at overo:/home/xerxes/llvm-test/fail/CodeGen/softenfloat# llvm-as < 2007-11-19-VectorSplitting.ll | llc > SoftenFloatResult #0: 0x614e00: f32 = undef > llc:

Hi, Simple One schrieb: > 1. Can some one tell me if LLVM ARM is being used by anyone to compile > any shipped products? If so, > a) how are you getting by despite the apparent bugs that exist > (http://llvm.org/bugs/buglist.cgi?quicksearch=ARM)? I want to use llvm inside OpenJDK's runtime hotspot for which a variant exists that uses llvm as a JIT compiler backend.

Christophe Avoinne wrote: > Hi, > > - Cortex-A8 needs a specific instruction scheduler as dual issue forces > you to interleave some instructions to allow to run two instructions in > the same cycle for the best performance (Cortex-A9 is out-of-order so > dual issue is not an issue (!) for performance). > - Cortex-A8/A9 have several useful new instructions : for instance,

Hi Sorry, the reason I joined the list is for help finding a bug that occurs when libvorbisenc is compiled and run on ARM EABI systems (current Debian, Gentoo, OpenEmbedded etc). The symptom is that oggenc produces shorter ogg files than it should (about 1/2 size) that decode to the correct duration but of total silence. libvorbis/examples/encoder_example does the same on these systems, but

Hello, I wonder if it's possible to cross compile regular linux packages (autotools based) into llvm bitcode. Such bitcode could run on multiple target platforms using lli. So for example if we take 'tar' sources and compile them, we have 'tar' bitcode. We can run it using 'lli tar'. If it was possible in general, then probably building lots of linux packages could be

Hello Out of curiosity, has someone managed to run Asterisk on a Beagleboard for home-use? www.beagleboard.org As an alternative to a PC, it can be powered from a USB hub, so that would make for a compact, fanless Asterisk server. Thank you.

Hi Rafal, LLVM's bitcode is not target independent in the manner you're hoping for. You can't take bitcode generated for x86 and use it on ARM, for example, or bitcode generated for Linux and use it on Darwin. -Jim On Jun 18, 2011, at 4:10 PM, Rafal Rusin wrote: > Hello, > > I wonder if it's possible to cross compile regular linux packages > (autotools based) into

hello vorlon, got notified of your patch, will apply next days upstream unless some critiques are voiced on ml. thanks. -- maks ----- Forwarded message from Steve Langasek <steve.langasek at canonical.com> ----- Date: Wed, 16 Feb 2011 22:05:42 -0000 From: Steve Langasek <steve.langasek at canonical.com> Subject: [Bug 527720] Re: thumb2 porting issues identified: klibc uses

Sandeep Patel wrote: > My goal is to have Cortex-A9 support complete in far less than three > months. I've recently gotten some additional help toward that goal, so > the pace should pick up soon. > > As far as compiler texts, there are many newer texts to recommend as > just about all the major optimization passes are done differently > after SSA-form appeared in about

Use klibc way to define a system dependent preprocessor definition: disabled by default and enabled for newer arm. Based on a patch by vorlon that got tested on his beagleboard, should be functional equivalent. Fixes: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/527720 Cc: Steve Langasek <steve.langasek at canonical.com> Cc: Kirill A. Shutemov <kirill at shutemov.name> Cc: