search for: elf_x86_64

...nd 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...` files) which ld selecte...

...strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

...l try to solve it later. Here is the reproduction script for x86_64 host: $ cat test.cc template <class T> void foo(T) {} int main() { foo(0); foo(1.0); } $ clang++ -c test.cc -fno-unique-section-names $ lld -flavor gnu -target x86_64 --hash-style=both --build-id \ --eh-frame-hdr -m elf_x86_64 \ -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o a.out \ <bunch of regular linker arguments here> $ ./a.out Illegal instruction $ clang++ -c test.cc -funique-section-names $ lld -flavor gnu -target x86_64 --hash-style=both --build-id \ --eh-frame-hdr -m elf_x86_64 \ -dynamic-linker /...

...clude -I/home/test1/xen-unstable/xen/include/asm-x86/mach-generic -I/home/test1/xen-unstable/xen/include/asm-x86/mach-default -msoft-float -mno-red-zone -fpic -fno-reorder-blocks -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -D__ASSEMBLY__ -c exits.S -o exits.o ld -m elf_x86_64 -r -o built_in.o exits.o make[8]: Leaving directory `/home/test1/xen-unstable/xen/arch/x86/hvm/svm/x86_64'' ld -m elf_x86_64 -r -o built_in.o emulate.o intr.o svm.o vmcb.o x86_64/built_in.o make[7]: Leaving directory `/home/test1/xen-unstable/xen/arch/x86/hvm/svm'' make -f /home/t...

Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/crti.o /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/crtbegin.o -L /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib -L /usr/lib/gcc/x86_64-alpine-l...

...strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppo...

...supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes &...

...checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

...checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

...checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

...wrote: > Alpine linux is a distribution that uses musl libc instead glibc. Here are > my steps to reproduce: > > On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, > and build them from source. > > $ clang -c hello_world.c > $ ld.lld --gc-sections -m elf_x86_64 -o hello_world > /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o > /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/crti.o > /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/crtbegin.o -L > /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib -L > /us...

...s a distribution that uses musl libc instead glibc. Here >> are my steps to reproduce: >> >> On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, >> and build them from source. >> >> $ clang -c hello_world.c >> $ ld.lld --gc-sections -m elf_x86_64 -o hello_world >> /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o >> /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/crti.o >> /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/crtbegin.o -L >> /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../.....

...'ve just fixed a bug where when running on a x32 host the Environment part of the Triple is always GNUX32, I've now changed it so that it gets properly set to GNU. This *fixes* the -m64 case, since otherwise it *always* tries to compile to ILP32 except for some reason the object ends up as elf_x86_64, not sure why yet... (can anybody help here?) The -m32 case worked because then the Arch component was set to i386 which is !=x86_64 as protects all the GNUX32 tests for throughout the patch. The upshot of this is the x86_64 target is now working on x32 hosts for the first time! :-) Unfortunately...

...if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/x86_64-suse-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

..... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

..... strip checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppo...

In the R-2.3.0 directory, what do you get if you type bin/R? Does R starts up OK, or do you get an error? What were the last few lines of output from running configure? Andy _____ From: Pramod Anugu [mailto:pramod.r.anugu@jsums.edu] Sent: Wednesday, May 31, 2006 11:23 AM To: Liaw, Andy; 'Andrew Perrin' Cc: r-help@stat.math.ethz.ch Subject: RE: [R] Running R [Broadcast]

...strip... strip checking if gcc static flag works... yes checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... yes checking if gcc supports -c -o file.o... yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool suppor...

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

This patch is still not creating elf32_x86_64 objects. No idea why. :( It does however, fix elf_x86_64 (-m64) code generation on x32 hosts which is nice. :) --- ./tools/clang/include/clang/Driver/Options.td.orig 2013-05-16 21:51:51.286129820 +0000 +++ ./tools/clang/include/clang/Driver/Options.td 2013-05-16 21:53:24.875004239 +0000 @@ -841,6 +841,7 @@ HelpText<"Enable hexagon-qdsp6 backw...