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

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 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 +-

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.

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 >>

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 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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Khem Raj (1): drmmode_output_dpms: Replace logical && with bitwise & operation Rob Clark (1): NEWS: Bump version to 0.4.4 Robert Nelson (1): add support for AM572x in the DDX Steve Wilkins (2): drmmode: Fix crash with multi-crtc page-flip drmmode: Fix leaked fb in case of failed pageflip

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam Jackson (1): Adapt Block/WakeupHandler signature for ABI 23 Hans De Goede (1): Use NotifyFd for drm fd Michel Dänzer (1): Adapt to XF86_CRTC_VERSION 7 Rob Clark (1): NEWS: Bump version to 0.4.5 git tag: xf86-video-omap-0.4.5

On Wed, Apr 15, 2015 at 5:08 PM, Isaiah Norton <isaiah.norton at gmail.com> wrote: >> Any thoughts of including lli in the nightly snapshot/package builds, for >> those of us embedding the JIT? > > > +1. I've wanted this (and llc) several times recently for debugging IR > issues on Windows. The Windows snapshots are targeted at users who want to try out an LLVM

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rob Clark (5): dri2: fix some leaks fix issue on pre-rotation kernel remove unneeded DRI1 dependency in configure.ac dri2: fix potential loop issue with triple buffer flip NEWS: Bump version to 0.4.3 git tag: xf86-video-omap-0.4.3 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-omap-0.4.3.tar.bz2 MD5:

On Tue, Apr 14, 2015 at 7:24 AM, Lang Hames <lhames at gmail.com> wrote: > > > There are two other Orc-based JITs in tree. One is the MCJIT replacement, > which you'll find in lib/ExecutionEngine/Orc/OrcMCJITReplacement.*, and the > other is OrcLazyJIT, which you'll find in tools/lli/OrcLazyJIT.*. The > former is just emulating MCJIT's behaviour, the latter is

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:

Hello, in OpenEmbedded we build kexec-tools and kexecboot statically linked against klibc. So we gathered some patches for klibc_1.5.15 here: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/klibc Patches and utils have been added (wc, losetup, modprobe) as well as fs-detection for vfat and jffs2. Perhaps someone can find something useful... We are waiting for the 1.5.16 release