similar to: Cross-compiling syslinux

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

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

----- Original Message ---- > From: Chuck Robey <chuckr at telenix.org> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Friday, May 22, 2009 9:22:53 AM > Subject: Re: [LLVMdev] Arm port > > OK, I've got enough to go on with, and I'm getting ready right now to begin > reading the dragon book, but one question bothers me regarding the

Hats off to the Android NDK team! http://developer.android.com/tools/sdk/ndk/index.html Important changes: * Added the Clang 3.1 compiler to the NDK. The GNU Compiler Collection (GCC) 4.6 is still the default, so you must explicitly enable the Clang compiler option as follows: * For ndk-build, export NDK_TOOLCHAIN_VERSION=clang3.1 or add this environment variable setting

Samuel Crow wrote: > > > > > ----- Original Message ---- >> From: Chuck Robey <chuckr at telenix.org> >> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> >> Sent: Friday, May 22, 2009 9:22:53 AM >> Subject: Re: [LLVMdev] Arm port >> >> OK, I've got enough to go on with, and I'm getting ready right now to begin

Hi, I'm trying to compile llvm/clang so that: it is compiled on osx 10.6, it runs on osx, but it outputs win32 objects. More exactly, I'm building an app which generates a .c file that doesn't include or link with anything, and I'd like to be able to make a win32 .dll of it on osx. Below is what I'm getting. Full log is here: http://pastebin.com/KsPGvAfW It fails while

Hi Steve, I don't know if syslinux is x86-only by design, or just by circumstance. Simply put, I like syslinux because it's simple and it works. I know that once I get it working, I can just edit a config file and put kernels/initrds in the right place. Grub2 is trash[1], and UEFI is awkward and uncomfortable to actually use - in that I have to currently have my kernel and initrd on

Replying to my own mail as I subscribe to the ML after the answer came, and thus never received it in my mailbox. On Wed, 5 Apr 2017 16:32:04 +0200 Beno?t Allard <benoit.allard at greenbone.net> wrote: > 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

cc +andrewhsieh +loganchien On Tue, Nov 13, 2012 at 11:21 PM, Joe Abbey <jabbey at arxan.com> wrote: > Hats off to the Android NDK team! > > Thanks for including me here, but I'd like to clarify that this is all from the really hard work of Andrew Hsieh and Logan Chien, and a few other Android engineers. (I'm actually not working on Android anymore, Andrew and Logan have

The current behavior is to not specify any toolchain and invoke CMake without additional arguments for configuring the NATIVE portion of the build. However, CMake will actually set the CC, CXX, and FC environment variables to full paths of the compilers in the CMAKE_{C,CXX,Fortran}_COMPILER CMake variables inside the CMake process. This results in those variables being propagated to any

Hello Irune, I tried to reproduce your command line options on a simple c file containing some floating point instructions using the clang-3.8 binary I have on my Ubuntu 16.04 machine with ARM_SYSROOT and ARM_GCC_TOOLCHAIN configured to point at a Linaro Hard float toolchain and clang used the hard float abi as expected. My clang-3.8 also accepted -mfloat-abi=hard. With my gcc toolchain the

I've been occasionally trying to build the FreeBSD base system (on amd64 / x86_64) using lld in order to see how things are progressing. With a few hacks in the FreeBSD build I can now link the base system userland. The missing functionality I had to work around is listed below. Some of these should probably be addressed in our FreeBSD build infrastructure, while others should be handled in

Hi There, I am trying to build a cross-compiler for an architecture with MIPS like ISA. To begin with, I built a toolchain for MIPSr2 which uses: Clang-3.1 for preprocessing, compiling, optimizing; Binutils-2.22 for assembling and linking; Newlib-1.20.0 as the standard C library implementation. I modified the Clang Driver to use the correct binutils tools and linker scripts. Compiling Newlib with

Hi all, with reference to the reply below, I downloaded toolchain from codesourcery (arm-2009q1-203-arm-none-linux-gnueabi) with gcc 4.3.3... when i compile llvm+clang with this toolchain i am getting the following error make[4]: Entering directory `/home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm-obj/tools/clang/tools/c-index-test' llvm[4]: Linking Release executable c-index-test (without

Prasanth J wrote: > > Hi all, > with reference to the reply below, I downloaded toolchain from > codesourcery (arm-2009q1-203-arm-none-linux-gnueabi) with gcc 4.3.3... > when i compile llvm+clang with this toolchain i am getting the > following error > > make[4]: Entering directory >

On 05-08-15 12:05, Gene Cumm wrote: > > I recompiled with this in mk/devel.mk <http://devel.mk>: > > GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 > > 0x2f8 is a BIOSism. Is this a problem? The example in the comments said 0x3f8 which is COM1.

Hallo, syslinux, I've just tried to compile syslinux 4.04 for slackware - it stopped when it tried to execute Entering directory `/path/to/diag/geodsp' ./mk-lba-img lba.img "strace" shows execve("./mk-lba-img", ["./mk-lba-img", "lba.img"], [/* 49 vars */]) = - 1 ENOEXEC (Exec format error) dup(2) = 3

On 12 March 2018 at 16:35, Son Tuan VU via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Thanks for your prompt reply. > > I didn't build the libc at all, I downloaded a pre-built version of the > whole toolchain from > https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads, so I > guess it is an official version provided by ARM and should work? This >

Hi, I can able to compile LLVM using armgcc_4.3.3 (codesourcery2009q1..).. but when i tried to run it on target it shows GCC 4.3.0 version not found. So i copied the runtime libraries (libc.so and libgcc_s.so) from the toolchain to the target and exported its path in LD_LIBRARY_PATH. But when i tried to run any llvm tools on target its crashing with Segmentation fault. What could be the problem

Hi, As you said i downloaded arm toolchain from codesourcery(2009q3 with gcc 4.4.1 version).. if i use this toolchain i am getting the following error.. make[2]: Entering directory `/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis' llvm[2]: Compiling LoopPass.cpp for Release build if arm-none-linux-gnueabi-g++ -I/home/prasanth/LLVM_ARM/llvm-with-armgcc433/llvm/include