From: Brian Raiter <breadbox@muppetlabs.com>
To: linux-assembly@vger.kernel.org
Cc: fsshl@luxmail.com
Subject: Re: simple hello.asm (NASM) not compile in x64, plz help
Date: Fri, 28 Nov 2014 21:26:56 -0800 [thread overview]
Message-ID: <21625.22816.280077.588423@eidolon.muppetlabs.com> (raw)
In-Reply-To: <20141128203537.80F63DB6@m0005299.ppops.net>
>
> ld -s -o heworl heworl.o
> ld:i386 architecture of input file *.o is incompatible with i386:x86-64 output
You told nasm to create a 32-bit .o file. Tell nasm to create a 64-bit
.o file instead. Use "-f elf64" instead of "-f elf32".
The command "nasm -hf" will display all the valid output formats that
nasm supports.
b
next prev parent reply other threads:[~2014-11-29 5:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 4:35 simple hello.asm (NASM) not compile in x64, plz help eric lin
2014-11-29 5:26 ` Brian Raiter [this message]
2014-12-24 19:49 ` Robert Plantz
-- strict thread matches above, loose matches on Subject: below --
2014-11-29 10:20 Charles T. Bell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21625.22816.280077.588423@eidolon.muppetlabs.com \
--to=breadbox@muppetlabs.com \
--cc=fsshl@luxmail.com \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).