This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc's limits.h vs POSIX

From: DJ Delorie <dj at redhat dot com>
To: ian at wasabisystems dot com
Cc: gcc at gcc dot gnu dot org
Date: Wed, 21 Jan 2004 20:58:40 -0500
Subject: Re: gcc's limits.h vs POSIX
References: <200401220116.i0M1G5Ps019902@greed.delorie.com><Pine.LNX.4.58.0401220119540.15778@digraph.polyomino.org.uk><200401220139.i0M1d6kN026116@greed.delorie.com> <m31xpsg3m9.fsf@gossamer.airs.com>

> By default it looks in exactly one directory, SYSTEM_HEADER_DIR, which
> in a native compiler is by default /usr/include.  See LIMITS_H_TEST.
> In t-djgpp this is set to $(DJDIR)/include.  I don't know what sets
> DJDIR.

DJDIR is set by default for all DJGPP-hosted applications, it's part
of the runtime.  I'll have to figure out a better way to set that
variable; it's really only appropriate for djgpp natives, not crosses.

Sigh.

References:
- gcc's limits.h vs POSIX
  - From: DJ Delorie
- Re: gcc's limits.h vs POSIX
  - From: Joseph S. Myers
- Re: gcc's limits.h vs POSIX
  - From: DJ Delorie
- Re: gcc's limits.h vs POSIX
  - From: Ian Lance Taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]