search for: eblot

trying this: clang -march=armv7-a -mcpu=cortex-a9 -ccc-host-triple arm-none-linux -ccc-gcc-name arm-none-linux-gnueabi-gcc a.c 2010/9/10 Emmanuel Blot <eblot.ml at gmail.com>: > Hello, > > Is there a quick tutorial to build the LLVM toolchain from a Linux or > Mac OS X x86 host for an ARM v4/v5/v6 ELF target? > It this configuration supported, and is it possible to build the Clang > compiler for this host/target combination? > &g...

Hello, Is there a quick tutorial to build the LLVM toolchain from a Linux or Mac OS X x86 host for an ARM v4/v5/v6 ELF target? It this configuration supported, and is it possible to build the Clang compiler for this host/target combination? I know about the installation page, but I keep failing to build this toolchain with LLVM 2.7. Maybe it is not (yet) supported? Thanks, Manu

...daemon from the SWAT Web interface. This leads to the INTERNAL ERROR, see samba.oulx Now, to locate the problem, I tried the same kind of command on the same file, bugs.ps, but using the SMBCLIENT application from the Linux server itself, without changing anything, nor restarting the SMBd daemon: eblot@ouessant:~ > smbclient //ouessant/lexmark smb: \> print bugs.ps putting file bugs.ps as bugs.ps (162.6 kb/s) (average 162.6 kb/s) smb: \> exit (see complete log of this command in smbclient.log, attached) This command has successfully printed the file onto the printer ! (see the log file...

>> I'm used to build GCC (4.x) toolchains with newlib, but how can I do >> the same with llvm-gcc ? > Pretty much same way as with gcc. E.g. via --with-newlib, etc. I successfully built llvm+clang, but it seems that the newlib library files have neither been compiled nor installed. With GCC (at the time 4.5.2), the build steps are straightforward: newlib/ and libgloss/

Hi All, Is there a way to tell the LLVM configure script to append the version number as a suffix, so that clang and llvm executables are versioned - the same way GCC build scripts do - e.g. clang -> clang-3.3 ? I'm looking for a solution so that the default clang toolchain that comes with OS X not to conflict with an SVN-originated, locally build clang version when both toolchains are

Hi, Is there a way to (cross-)build the compiler-rt for an ARM-EABI target? I read the comments in the associated Makefile, so I understand it cannot be easily done when builing clang. However, is there a way to build the compiler-rt for another plaftorm but the host, once clang & llvm have been successfully built? Thanks, Manu.

> Virtually all. As far as I could test, all major architectures > (v4/v5/v6 + v7-A-R-M), although I'm still fighting with some Thumb > code generation. Not a big issue for me: targets are ARMv4 (ARM7) and ARMv5 (ARM9) "classic" CPUs - in ARM terminology. No cortex. > I haven't tested dragonegg, but clang and llvm-gcc do the job. > llvm-gcc seems to be more in

> There isn't one at the moment, ideally it should figure it out, but I haven't looked much into it - it may be that this isn't working yet. I should say that I'm still a bit confused: Is it possible to build for ARM CPUs now? 1/ from which hosts (x86-*-* ?) 2/ for which targets (arm-*-* ?) 3/ what are the supported tools for ARM targets: a/ llvm-gcc (gcc 4.2)?