delorie.com/archives/browse.cgi | search |
From: | dontmailme AT iname DOT com (Steamer) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: 3rd Try: Maybe an asm problem? (Problems linking) |
Date: | Fri, 28 Apr 2000 19:58:10 GMT |
Organization: | always disorganized |
Lines: | 18 |
Message-ID: | <3909ed43.42944527@news.freeserve.net> |
References: | <39096460 DOT 1D069B39 AT pop DOT gis DOT net> <390969a0 DOT 9237112 AT news DOT freeserve DOT net> <3909DAFE DOT CADFC30F AT pop DOT gis DOT net> |
NNTP-Posting-Host: | modem-58.golden-cleaner.dialup.pol.co.uk |
X-Trace: | news5.svr.pol.co.uk 956951891 2554 62.137.19.58 (28 Apr 2000 19:58:11 GMT) |
NNTP-Posting-Date: | 28 Apr 2000 19:58:11 GMT |
X-Complaints-To: | abuse AT theplanet DOT net |
X-Newsreader: | Forte Free Agent 1.11/32.235 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Joseph Rose wrote: >I have described what the asm source code looks like. Only very vaguely. My NASM files look like that too, but they work. How have you declared the segments? >If you need more, I can publish a function in question and >the beginning of the file. Go on then. Looking at your other post, however, your problem may be elsewhere. The prototypes for your asm functions need to be wrapped in extern "C" {} if you're using C++, unless you've taken name-mangling into account in your asm file. S.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |