X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OwZlyPWBy/cSoRCEu1FlIJTbVoxpJLQIrvKg6dZ66EU=; b=gUIAOsyHwsQ+wht9ZMiZptS1m2Oocy1lZ4S3FqvFR+FKSOqaZuZ0ayv2nakolnKmE+ CP2y6Fg9vECRsXQrLyMrSxSaHJ0sjKWJJGaXLGEFqhqAALTIvUpYGhWxaHXG0oeUQJjH OQVKnDtfqxGeWBKzF3Eaq5lopF9q7Qu6sxrrjQoZdQUAy/AQOnT/1VWIKOKurYNJAFjJ pehaf3/SBrHGt60Ih9nKrxYBKkMFdDKA5Zt+2SE8cWRPcQ+YliBiUSMJPG3ONbwTVivU PRDFTe9kT3quqfPLtgiNg7DJqPuO+pitLGwxooG7/zYm9G3fOo/5H5XNKxyy3s/nTT24 uXtA== MIME-Version: 1.0 X-Received: by 10.60.45.207 with SMTP id p15mr14247765oem.34.1434775049912; Fri, 19 Jun 2015 21:37:29 -0700 (PDT) In-Reply-To: <073e9ce1-d1a5-4b89-8a84-447e013d021c@googlegroups.com> References: <201506091712 DOT t59HCPci004068 AT delorie DOT com> <557739E0 DOT 6070608 AT gmail DOT com> <55775E64 DOT 2090901 AT gmail DOT com> <5579ED42 DOT 6070309 AT gmail DOT com> <5579FE8D DOT 3080501 AT gmail DOT com> <557B436F DOT 1050101 AT gmx DOT de> <779efaf6-8ebf-4f2a-a526-a2773e3909b4 AT googlegroups DOT com> <4131b54f-b34d-4a84-ada6-3443ed9efce9 AT googlegroups DOT com> <20150618-004800 DOT 313 DOT 0 AT Your-Name-Here DOT News> <65ad24c7-0888-4526-9395-e262f348a021 AT googlegroups DOT com> <5584B697 DOT 60303 AT gmail DOT com> <073e9ce1-d1a5-4b89-8a84-447e013d021c AT googlegroups DOT com> Date: Fri, 19 Jun 2015 21:37:29 -0700 Message-ID: Subject: Re: DJGGP 2.05 upgrade problems. (appologies) From: "Louis Santillan (lpsantil AT gmail DOT com)" To: "djgpp AT delorie DOT com" Content-Type: text/plain; charset=UTF-8 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 I'd argue, again, the headers have unexpected behavior (in comparison to linux), in the best case. Looking at the two files [0][1], there's no mention of __STRICT_ANSI__ in the glibc version. [0] http://www.delorie.com/bin/cvsweb.cgi/djgpp/include/fcntl.h?rev=1.11 [1] https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=blob_plain;f=io/fcntl.h;hb=HEAD On Fri, Jun 19, 2015 at 6:16 PM, RayeR (glaux AT centrum DOT cz) wrote: >> Like you mentioned, you have to use gcc 4 as 5 has issues with multiple >> extern defines. > > I guess it could be cured by adding some -std=gnu99 to CFLAGS or how it is correct to properly interpret inline functions as gcc 5.x needs __inline__ __attribute__ ((__gnu_inline__))