search for: elf_l1om

I have installed dom0 Wheezy 64 bit on Dell PowerEdge T310 with kernel from package and xen-unstable. System is in Uefi mode and booted with grub-efi-amd64. Booting without xen efibootmgr works, while with xen not, efivars kernel module is loaded but show this message: efibootmgr Fatal: Couldn''t open either sysfs or procfs directories for accessing EFI variables. Try ''modprobe

...sugests binutils doesn't support PE (EFI), which looks to be the case with the stock version on CentOS 7, note missing i386pe from the list of supported emulations: # ld -V GNU ld version 2.25.1-32.base.el7_4.2 Supported emulations: elf_x86_64 elf32_x86_64 elf_i386 i386linux elf_l1om elf_k1om I downloaded binutils 2.30 from http://ftp.gnu.org/gnu/binutils/ and built it with: yum -y groupinstall "Development Tools" tar xzf binutils-2.30.tar.gz cd binutils-2.30 ./configure --enable-targets=x86_64-pep make make install Now I have a version that supports i386pe: #...

Hi James, renato, So how do I download the missing ARM libraries on Ubuntu14.04? I cannot find any available libraries. Best, Liyang -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160425/04dfc553/attachment.html>

...lvm_clang/build/Debug+Asserts/bin/../lib/LLVMgold.so /tmp/hello-T8xLAt.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed crtend.o crtn.o /usr/bin/ld: unrecognised emulation mode: armelf_linux_eabi Supported emulations: elf_x86_64 elf32_x86_64 elf_i386 i386linux elf_l1om elf_k1om clang: error: linker command failed with exit code 1 (use -v to see invocation) 6. The problem occurred when clang starts to link with ld. Clang tried to use the ld in a wrong place - "/usr/bin/ld". So I tried it myself like below. /home/hum/Documents/Projects/llvm_clang/gnuar...

On Sat, Jun 16, 2012 at 08:20:23PM +0900, Journeyer J. Joh wrote: > If the cross compiling is supported, is there any documentation on how to > do it? The short version is: assuming you have a cross-binutils installation using e.g. x86_64--netbsd-as and x86_64--netbsd-ld, you add a symlink called x86_64--netbsd-clang to clang and just call that with an appropiate --sysroot to make it find

Hello list, I wonder if llvm/Clang can compile C or C++ for ARM from on x86. http://comments.gmane.org/gmane.comp.compilers.clang.devel/8896 The talk above answered 'NO' to my question, which means Clang is not yet able to cross compile for ARM on X86. Is the answer still correct for my question? I saw somewhere that Clang supports ARM on Darwin only. Then is the cross compiling

Hello > ./clang -v -emit-llvm -ccc-host-triple arm-none-linux-gnueabi > -I/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/include > -L/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin hello.c You forgot about sysroot here. > /home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin/ld: > unrecognised emulation mode: armelf_linux_eabi >

...9/lib/gcc/arm-none-linux-gnueabi/4.5.1/armv4t/crtend.o needs to be used!!!) /home/hum/Documents/Projects/arm_toolchain/arm-2010.09/arm-none-linux-gnueabi/libc/usr/lib/crtn.o /usr/bin/ld: unrecognised emulation mode: armelf_linux_eabi Supported emulations: elf_i386 i386linux elf32_x86_64 elf_x86_64 elf_l1om elf_k1om clang: error: linker command failed with exit code 1 (use -v to see invocation) Problem #1 : wrong linker! ld in cross toolchain is needed! Problem #2 : All libraries have to be of the cross toolchain! Problem #3 : All libraries have to be of the cross toolchain! (/home/hum/Documents/Pro...

...ne, these are found in `/usr/lib/ldscripts/` and there are quite a few of them. However, many share the same filename excluding the extension. On my machine, I see $ ls /usr/lib/ldscripts | sed 's/\.x[a-z]*$//' | sort | uniq -c 13 elf32_x86_64 13 elf_i386 13 elf_k1om 13 elf_l1om 13 elf_x86_64 5 i386linux These appear to correspond to different "supported emulations" (the `-m` option), since they align with the "Supported emulations" output of ld's `-V` option. The `-V` output also prints the default linker script (one of the `.x...` file...