X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Fri, 12 Jun 2015 10:28:36 +0300
From: "Eli Zaretskii (eliz AT gnu DOT org)" <djgpp AT delorie DOT com>
Subject: Re: DJGGP 2.05 upgrade problems.
In-reply-to: <mldu7c$i4l$1@speranza.aioe.org>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <838ubps7vf.fsf@gnu.org>
References: <201506091712 DOT t59HCPci004068 AT delorie DOT com> <557739E0 DOT 6070608 AT gmail DOT com> <CAB9Rao93XrKFBpUDnZdjCz+rEXHGOU2RNKdou2oMLJOk802LnA AT mail DOT gmail DOT com> <55775E64 DOT 2090901 AT gmail DOT com> <CAB9Rao-Njdr-CB=vqHnb+TVDmXu3eXqsB5CHB7V0kDwBEsM-WQ AT mail DOT gmail DOT com> <5579ED42 DOT 6070309 AT gmail DOT com> <mldu7c$i4l$1 AT speranza DOT aioe DOT org>
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

> From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
> Date: Fri, 12 Jun 2015 06:29:02 +0000 (UTC)
> 
> > In file included from F:/proj/q2dos/game/q_shared.h:40:0,
> >                           from client../qcommon/qcommon.h:23,
> >                           from client/ref.h:23,
> >                           from client/client.h:30,
> >                           from client/cl_input.c:22:
> > f:/djgpp_205/include/time.h:126:16: error: expected '=', ',', ';', 'asm' 
> > or '__attribute__' before 'unsigned'
> >   _EXTERN_INLINE unsigned long long
> >                                     ^
> 
> 1. Check the environment that you don't have _any_ refenrences to the
> old DJGPP. In bash I'd "env|less" and look carefully.
> 
> 2. Try adding -v to your flags and examine paths gcc uses to verify
> that they are right.
> 
> 3. It can be an error in the previous include file (I'm not sure which
> order gcc lists them; either q_shared.h or cl_input.c, I'd guess) that
> didn't terminate whatever it was trying to declare/define (as the
> compiler is looking for a possible ";").

It's usually best to invoke the same GCC command that was used to
compile the offending source file, but with -c replaced with -E and
with output redirected to some *.ii file, and then examine the
preprocessed source near the problematic place.