From: Greg Chicares <chicares@mindspring.com>
To: help-gcc@gnu.org
Subject: Re: Problems using g++ when using far modifier
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <38716312.E94AAEA3@mindspring.com> (raw)
Message-ID: <20000401000000.UglUBJg5SvbqKAN1gsQmAwnSeZ7u6NQ4YGYtbuPTXdY@z> (raw)
In-Reply-To: <20000103202834.12430.00000216@ng-fm1.aol.com>
> I can't compile whit g++ when I code a function or variable that needs to use
> the far, _far, __far, _far16, or __far16 modifiers. Is there an specific
> library file that I need to include?
I've never seen those used except in 16-bit programs.
If you want to compile a 32-bit program from source
that was originally written with a 16-bit environment
in mind, you can just
#define far
#define _far
and so on to eliminate them.
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-03 17:31 JHVasquez
2000-01-03 19:07 ` Greg Chicares [this message]
2000-04-01 0:00 ` Greg Chicares
2000-04-01 0:00 ` JHVasquez
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=38716312.E94AAEA3@mindspring.com \
--to=chicares@mindspring.com \
--cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).