X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	Martin Str|mberg <ams AT ludd DOT luth DOT se>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGGP 2.05 upgrade problems.
Date:	Fri, 12 Jun 2015 06:29:02 +0000 (UTC)
Organization:	Aioe.org NNTP Server
Lines:	36
Message-ID:	<mldu7c$i4l$1@speranza.aioe.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>
NNTP-Posting-Host:	WLZdEp4S2PR09rkVF8ILdg.user.speranza.aioe.org
X-Complaints-To:	abuse AT aioe DOT org
User-Agent:	tin/2.1.1-20120623 ("Mulindry") (UNIX) (Linux/3.2.0-4-amd64 (x86_64))
X-Notice:	Filtered by postfilter v. 0.8.2
Bytes:	2309
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

"Frank Sapone (emoaddict15 AT gmail DOT com)" <djgpp AT delorie DOT com> wrote:
> Hey guys, so I figured I might as well try to upgrade the Q2DOS project 
> to DJGPP 2.05 (we're using 2.03!).  I would like to add DX3 support for 

Thanks for testing!

> I made an entirely new DJGPP dir, got my paths all that, etc. setup 
> properly and afaik I have all the required tools.  When I try to build I 
> get this:

> 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 ";").


HTH,

-- 
MartinS

- Raw text -