This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC headers and DJGPP port
- To: gcc at gcc dot gnu dot org, Jeff Law <law at cygnus dot com>
- Subject: Re: GCC headers and DJGPP port
- From: Bruce Korb <bkorb at sco dot COM>
- Date: Mon, 17 Jul 2000 19:02:39 -0700
- CC: "Mark E." <snowball3 at bigfoot dot com>
- Organization: Santa Cruz Operations
- References: Your message of Mon, 17 Jul 2000 23:02:50 +0200. <200007172102.XAA07817@loewis.home.cs.tu-berlin.de> <39735DE7.6172.11E5F1@localhost>
- Reply-To: Bruce Korb <bkorb at gnu dot org>
"Mark E." wrote:
>
> > The "how" of this question is the port maintainer figures out the right
> > value and codes it into the target .h file. For example:
>
> Thanks for the info. Looking at the gcc source, the defaults already work
> fine, but since defaults can change so it's probably not a good idea to rely
> on it. I'll revise my current DJGPP config patch to include these
> definitions.
fixincludes really has the same issue. It is really quite obtuse
as to how I can pull:
#define PTRDIFF_TYPE "int"
out of, say, gcc/config/i386/linux.h. It would be nice to make
the ptrdiff_t, size_t and wchar_t hacks based on some well-known
file like "deduced.h". Unfortunately, these are not useful:
#define ptrdiff_t __PTRDIFF_TYPE__
#define size_t __SIZE_TYPE__
I guess my questions are, "Do the config/*/*.h files get mapped
or copied into a well-known name? How can I use them?"
:-)
Thanks!