X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Fri, 29 May 2015 08:58:02 +0300 From: "Eli Zaretskii (eliz AT gnu DOT org)" Subject: Re: ANNOUNCE: DJGPP 2.05 beta 1 In-reply-to: X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83k2vsvsb9.fsf@gnu.org> References: <201505042003 DOT t44K3odg011007 AT delorie DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Thu, 28 May 2015 15:00:35 -0700 > From: "Louis Santillan (lpsantil AT gmail DOT com)" > > In porting, I noticed that using `cc -std=c99` confuses the djgpp > headers such that the main bodies of the headers get nullified for > io.h, fcntl.h, and unistd.h. This is because `-std=c99` implies > `__STRICT_ANSI__` which is guarded against in those headers and > probably others. The simple work around is to instead use > `-std=gnu99` which does not imply `__STRICT_ANSI__` and brings in the > needed function prototypes (isatty(), setmode(), a couple others). Don't use -std=c99, unless you are building a program that doesn't use any features not in the ANSI C99 standard. I think you want -std=gnu99 instead. That option doesn't disable non-ANSI features, but does assume C99 features supported.