similar to: Extend Multiboot1 with support for ELF64 file format

This patch is just a (shameless) copy from bug #28 [1]. The original patch has been sitting there for a couple of years now, and it was based on Syslinux v 4.05. The patch I am posting here is just a re-base on v.6.03. Whichever inadequate formatting (tabs, trailing spaces...), or any kind of correction that was required for the original patch to be accepted, is probably still required now.

On Sat, Oct 10, 2015 at 11:14:27AM +0300, Ady via Syslinux wrote: > This patch is just a (shameless) copy from bug #28 [1]. > > The original patch has been sitting there for a couple of years now, > and it was based on Syslinux v 4.05. :-/ > The patch I am posting here is just a re-base on v.6.03. Whichever > inadequate formatting (tabs, trailing spaces...), or any kind

first off im running on an AMD64 3800+, Ubuntu 6.06, 2.6.15-25-amd64-generic ive been working on getting this thing to work for the past few hours, setup symbolic links like in the howto run wine on amd64 tutorial, plus some. and started compiling, make depend went well, and so was make all until this happened make[2]: Entering directory `/home/anolis/Desktop/wine-0.9.16/dlls/gdi'

Did you mean ld-new ? ld-new -v GNU gold (GNU Binutils 2.20.51.20100707) 1.9 ld-new --help ./ld-new: supported targets: elf32-i386 elf32-i386-freebsd elf64-x86-64 elf64-x86-64-freebsd elf64-sparc elf32-sparc elf64-powerpcle elf64-powerpc elf32-powerpcle elf32-powerpc elf32-bigarm elf32-littlearm On Mon, Jul 12, 2010 at 6:52 PM, Anton Korobeynikov <anton at korobeynikov.info > wrote:

objcopy needs "output-target" and "binary-architecture" parameters which makes it necessary to keep a list of known architectures. The bin2s.pl script generates input for the GNU assembler which should produce an object file that is equivalent to that produced by objcopy. I have successfully tested the change on an amd64 Debian/unstable system. --- helper/Makefile.am |

hello hpa, please pull latest git pull git://git.debian.org/~maks/klibc.git maks forgot to ask to keep git port open for our boxes at university, thus moved my tree over too the alioth box. for the changes maximilian attems (4): [klibc] klibc/socketcalls/.gitignore addition [klibc] elf.h add support for st_info field [klibc] remove local insmod.c copy [klibc] ipconfig

Hi Eric, The main thing we need to fix is that the selection between ELF32/ELF64 needs to depend on the ABI being N64 and not on whether we used a mips-linux-gnu triple versus a mips64-linux-gnu triple. So 'clang -target mips-linux-gnu' -mips64r2 -mabi=64' should produce an ELF64 and 'clang -target mips64-linux-gnu -mips32r2 -mabi=32' should produce an ELF32. In terms of code,

From: Sylvain Gault <sylvain.gault at gmail.com> These patches basically remove unused linker scripts and port a change that was made to an unused script. Those are to be applied on top of the gcc 5 bug fixes as they would conflict otherwise. Sylvain Gault (4): diag/mbr: fix dependency to linker script Remove unused linker scripts core: Make symbols defined in linker script HIDDEN

> In the case of the ELF writer, we want a similar structure. Anything that > can be simple exposed as data should be (e.g. whether the target is 32- or > 64-bit), anything more complex should be exposed as virtual methods that > are overloaded. The ELF spec makes it very clear what parts of the file > format are common across targets and what the variations are caused by.

When I try to build my existing application using winegcc, I get the following error message. /usr/bin/ld: Relocatable linking with relocations from format elf32-i386 (/usr/local/lib/wine/libwinecrt0.a(exe_entry.o)) to format elf64-x86-64 (vida_codecs.a8MfIW.o) is not supported winebuild: /usr/bin/ld -r failed with status 256 This application can be built from a 32 bit OS Linux without problem.

# Summary As a consequence of comparing the RISC-V LLVM MC assembler to the RISC-V GNU assembler I've noticed that a number of targets have quite different handling for pc-relative jumps/branches with immediate integer operands in llvm-mc vs GNU as. I'll admit that this isn't likely to occur in hand-written code (as you'd almost always prefer to use a label), but thought it was

> ld-new works only with those objects which are compiled using native gcc but > doesn't work for cross-compiler gcc/arm. Ok, please show: ld --version and last few lines of the ld --help output -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hi Eric, as I was working on the same issues that are covered in your patch I also made a change in clang driver to pass this option to the assembler. Could you please review it and tell me your opinion? http://reviews.llvm.org/D6091 Thanks Vladimir ________________________________ From: Daniel Sanders Sent: Wednesday, January 28, 2015 8:59 PM To: Eric Christopher; Vladimir Medic; llvmdev at

Hi, This is just a quick note that I receive effectively the same error when doing an amd64 build. A workaround is to install the binary package libxenstore3.0 but of course the source build should not require an external install of one of the packages that it builds. James

> Why isn't the ABI reflected in the triple? Unfortunately, there's no easy answer to that. Some targets are better than others but generally speaking triples are very ambiguous. For example, in (most) GCC mips-linux-gnu/mips64-linux-gnu toolchains both triples produce 32-bit big-endian binaries for MIPS-I by default. Vendors can override the majority of this so it's entirely

From: Geert Stappers <stappers at nero.gpm.stappers.nl> They were introduced by the patch for ELF64 support. --- com32/mboot/map.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/com32/mboot/map.c b/com32/mboot/map.c index 2e8641f..1992f14 100644 --- a/com32/mboot/map.c +++ b/com32/mboot/map.c @@ -281,7 +281,7 @@ struct multiboot_header *map_image(void *ptr, size_t

Hi, I've been having trouble properly resolving an issue with our assembly syntax. The prefix our assembler uses for private local/global labels depends on the object file format. For ELF32 they begin with '$' and for ELF64 they begin with '.L'. The object file format depends on the ABI, but multiple ABI's are usable with the same target triple so we can't select

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

All, I am running xen3.0.2 and xen unstable on RHEL 4, and get this error when trying to boot Xen kernel(domain0) ...... Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempting to kill init! Then system reboot.In grub.conf,I have

Yes, I'm following this page only and did whatever is mentioned there. On Mon, Jul 12, 2010 at 6:57 PM, Sanjeev chugh <sanjuchugh at gmail.com> wrote: > Did you mean ld-new ? > > ld-new -v > GNU gold (GNU Binutils 2.20.51.20100707) 1.9 > > ld-new --help > ./ld-new: supported targets: elf32-i386 elf32-i386-freebsd elf64-x86-64 > elf64-x86-64-freebsd elf64-sparc