Mail Archives: djgpp/2004/04/02/04:30:57
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f
|
From: | Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: compile problem using djgpp with nasm
|
Date: | 2 Apr 2004 09:21:35 GMT
|
Organization: | Aachen University of Technology (RWTH)
|
Lines: | 20
|
Message-ID: | <c4jbav$35m$3@nets3.rz.RWTH-Aachen.DE>
|
References: | <c4ilmp$1421$1 AT mail DOT cn99 DOT com>
|
NNTP-Posting-Host: | ac3b07.physik.rwth-aachen.de
|
X-Trace: | nets3.rz.RWTH-Aachen.DE 1080897695 3254 137.226.33.205 (2 Apr 2004 09:21:35 GMT)
|
X-Complaints-To: | abuse AT rwth-aachen DOT de
|
NNTP-Posting-Date: | 2 Apr 2004 09:21:35 GMT
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
xingqk <xingqk AT yahoo DOT com DOT cn> wrote:
> because these file have been compiled successfully under LINUX (gcc
> nasm ),so the include file can not be wrong ,
This assertion is, unfortunately, wrong. You're assuming that DJGPP
behaves *exactly* like Linux, in all the aspects that would concern
your program. There's no particular reason that should be the case.
> I list the symbol table of sys.o using the commond: nm sys.o
Looking at clock.o would be more instructive. Your problem almost
certainly is that the ABI (application binary interface), i.e. the
conventions ruling how C semantics are mapped to machine language,
and C names to symbol names to assembly-code names, is different
between Linux and DJGPP.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -