From: "Hans" <hans64@ht-lab.com>
To: linux-8086@vger.kernel.org
Subject: ld86 link sequence
Date: Fri, 2 Sep 2005 16:57:15 +0100 [thread overview]
Message-ID: <00a701c5afd7$049f5ef0$6402a8c0@dionysus> (raw)
Hi All,
If I use:
bcc -0 -ansi -Md -o test.com test.c
then all is OK and I can run test.com in a DOS box. However, I would like to
split the process into a separate compile and link stage which gives me a
better control over what will be linked in. I use the following command
syntax:
bcc -0 -ansi -c -Md -o test.o test.c
ld86 -d -s -L/lib/ -Olibdos.a -o test.com crt0.o test.o
The test.com file consist of the test.o code followed by msdos.o followed by
crt0.o. For some reason the first instruction in the file is not a jump to
crt0.o.
I tried different permutations of the above ld86 command arguments but they
all produce the same results. Can anybody spot what I am doing wrong?
Thanks,
Hans.
reply other threads:[~2005-09-02 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='00a701c5afd7$049f5ef0$6402a8c0@dionysus' \
--to=hans64@ht-lab.com \
--cc=linux-8086@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