views:

412

answers:

1

I have a sample assembly file that I compile with nasm:

nasm -f elf syscall.asm 

This generates a syscall.o file. I try to link it with ld:

ld -o syscall syscall.o

The ld command fails with the following error:

ld: i386 architecture of input file `syscall.o' is incompatible with i386:x86-64 output

However, if I do

ld -o syscall syscall.o -melf_i386

the command succeeds and I get a syscall executable.

Figuring out that nasm is not generating object code in x86-64 format I added "BITS 64" directive to the beginning of the syscall.asm file.

Then attempting to assemble syscall.asm with nasm gave the following error:

error: elf output format does not support 64-bit code

That seems strange because doing "file /usr/bin/nasm" on my terminal gives:

/usr/bin/nasm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped

My 64-bit Fedora Core 11 has the latest version of nasm installed and my CPU is Intel Core 2 Duo E7200.

[EDIT]

My question is how do I get nasm to emit object files that is compatible with i386:x86-64.

+1  A: 

Try using elf64 as the output format.

Example run:

$ cat elf64.asm
section .text
        jmp [rax]
$ nasm -f elf64 elf64.asm
$ objdump -Sr elf64.o

elf64.o:     file format elf64-x86-64


Disassembly of section .text:

0000000000000000 <.text>:
   0:   ff 20                   jmpq   *(%rax)
Chris Jester-Young
Wow, that worked. Thanks.
ardsrk