Re: [Warzone-dev] Bison warnings

2007-04-09 Thread Dennis Schridde 
Am Montag, 9. April 2007 schrieb Dennis Schridde:
> There are quite a few bison warnings...
Probably it is better when we also know the command that caused them:

bison -y  -d -oresource_parser.tab.h resource_parser.y
resource_parser.y: warning: conflicting outputs to file `resource_parser.tab.h'

bison -y  -d -ostrres_parser.tab.h strres_parser.y
strres_parser.y: warning: conflicting outputs to file `strres_parser.tab.h'

bison -y  -d -oscript_parser.tab.h script_parser.y
conflicts: 284 shift/reduce, 11 reduce/reduce
script_parser.y: warning: conflicting outputs to file `script_parser.tab.h'

bison -y  -d -ochat_parser.tab.h chat_parser.y
chat_parser.y:234.8-11: warning: symbol _T_A redeclared
conflicts: 69 shift/reduce, 36 reduce/reduce
chat_parser.y: warning: conflicting outputs to file `chat_parser.tab.h'

bison -y  -d -oscript_parser.tab.c script_parser.y
conflicts: 284 shift/reduce, 11 reduce/reduce

bison -y  -d -ochat_parser.tab.c chat_parser.y
chat_parser.y:234.8-11: warning: symbol _T_A redeclared
conflicts: 69 shift/reduce, 36 reduce/reduce

bison -y  -d -oaudp_parser.tab.h audp_parser.y
conflicts: 7 shift/reduce, 2 reduce/reduce
audp_parser.y:117.60: warning: rule never reduced because of conflicts: 
anim_file_list: /* empty */
audp_parser.y: warning: conflicting outputs to file `audp_parser.tab.h'

bison -y  -d -oaudp_parser.tab.c audp_parser.y
conflicts: 7 shift/reduce, 2 reduce/reduce
audp_parser.y:117.60: warning: rule never reduced because of conflicts: 
anim_file_list: /* empty */

bison -y  -d -oscriptvals_parser.tab.h scriptvals_parser.y
conflicts: 4 shift/reduce
scriptvals_parser.y: warning: conflicting outputs to file 
`scriptvals_parser.tab.h'

bison -y  -d -oscriptvals_parser.tab.c scriptvals_parser.y
conflicts: 4 shift/reduce


pgpxgUBGLDaGa.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Dennis Schridde 
Extra warnings are nearly all unused parameter related,
only a few are caused by signed/unsigned comparisons:

resource_parser.y: warning: conflicting outputs to file `resource_parser.tab.h'
strres_parser.y: warning: conflicting outputs to file `strres_parser.tab.h'
conflicts: 284 shift/reduce, 11 reduce/reduce
script_parser.y: warning: conflicting outputs to file `script_parser.tab.h'
chat_parser.y:234.8-11: warning: symbol _T_A redeclared
conflicts: 69 shift/reduce, 36 reduce/reduce
chat_parser.y: warning: conflicting outputs to file `chat_parser.tab.h'
script_lexer.lex.c: In function ‘yy_get_next_buffer’:
script_lexer.lex.c:2196: warning: comparison between signed and unsigned
conflicts: 284 shift/reduce, 11 reduce/reduce
chat_parser.y:234.8-11: warning: symbol _T_A redeclared
conflicts: 69 shift/reduce, 36 reduce/reduce
dec130.c:25: warning: unused parameter ‘rpl’
dec130.c:25: warning: unused parameter ‘_in’
dec130.c:26: warning: unused parameter ‘in_size’
dec130.c:26: warning: unused parameter ‘out’
rpl_reader.c:229: warning: unused parameter ‘rpl’
rpl_reader.c:229: warning: unused parameter ‘buffer’
rpl_reader.c:229: warning: unused parameter ‘buffer_size’
rpl_reader.c:233: warning: unused parameter ‘buffer’
rpl_reader.c:233: warning: unused parameter ‘buffer_size’
rpl_reader.c:322: warning: unused parameter ‘rpl’
sequence_stub.c:83: warning: unused parameter ‘startTime’
sequence_stub.c:83: warning: unused parameter ‘perfMode’
sequence_stub.c:105: warning: unused parameter ‘startTime’
sequence_stub.c:105: warning: unused parameter ‘lpBF’
sequence_stub.c:105: warning: unused parameter ‘perfMode’
sequence_stub.c:135: warning: unused parameter ‘skip’
sequence_stub.c:135: warning: unused parameter ‘subMin’
sequence_stub.c:135: warning: unused parameter ‘subMax’
sequence_stub.c:155: warning: unused parameter ‘skip’
sequence_stub.c:155: warning: unused parameter ‘subMin’
sequence_stub.c:155: warning: unused parameter ‘subMax’
piedraw.c: In function ‘pie_DrawShadow’:
piedraw.c:577: warning: comparison between signed and unsigned
conflicts: 7 shift/reduce, 2 reduce/reduce
audp_parser.y:117.60: warning: rule never reduced because of conflicts: 
anim_file_list: /* empty */
audp_parser.y: warning: conflicting outputs to file `audp_parser.tab.h'
conflicts: 7 shift/reduce, 2 reduce/reduce
audp_parser.y:117.60: warning: rule never reduced because of conflicts: 
anim_file_list: /* empty */
audio.c:59: warning: missing initializer
audio.c:59: warning: (near initialization for ‘g_sPreviousSample.z’)
audio.c:977: warning: unused parameter ‘iTrack’
audio.c:990: warning: unused parameter ‘iTrack’
audio.c:990: warning: unused parameter ‘iPan’
audio.c:1003: warning: unused parameter ‘iTrack’
audio.c:1003: warning: unused parameter ‘iVol’
audio.c:1016: warning: unused parameter ‘iTrack’
audio.c:1016: warning: unused parameter ‘iFreq’
cdaudio.c:104: warning: unused parameter ‘datasource’
cdaudio.c:104: warning: unused parameter ‘offset’
cdaudio.c:104: warning: unused parameter ‘whence’
openal_track.c:325: warning: unused parameter ‘datasource’
openal_track.c:559: warning: unused parameter ‘psSample’
openal_track.c:559: warning: unused parameter ‘szFileName’
openal_track.c:559: warning: unused parameter ‘iVol’
openal_track.c:577: warning: unused parameter ‘psSample’
openal_track.c:577: warning: unused parameter ‘iPan’
openal_track.c:585: warning: unused parameter ‘iVol’
openal_track.c:607: warning: unused parameter ‘iX’
openal_track.c:607: warning: unused parameter ‘iY’
netaudio_stub.c:32: warning: unused parameter ‘pSoundBuffer’
netaudio_stub.c:40: warning: unused parameter ‘pSoundData’
netaudio_stub.c:40: warning: unused parameter ‘soundBytes’
netaudio_stub.c:40: warning: unused parameter ‘bStream’
netplay.c:368: warning: unused parameter ‘pSize’
netplay.c:375: warning: unused parameter ‘pSize’
netplay.c:676: warning: unused parameter ‘guarantee’
netplay.c:723: warning: unused parameter ‘guarantee’
netplay.c:973: warning: unused parameter ‘addr’
netplay.c:992: warning: unused parameter ‘lpConnection’
netplay.c:999: warning: unused parameter ‘Lob’
netplay.c:1332: warning: unused parameter ‘async’
tip.c:73: warning: unused parameter ‘psScreen’
tip.c:73: warning: unused parameter ‘red’
tip.c:73: warning: unused parameter ‘green’
tip.c:73: warning: unused parameter ‘blue’
conflicts: 4 shift/reduce
scriptvals_parser.y: warning: conflicting outputs to file 
`scriptvals_parser.tab.h'
conflicts: 4 shift/reduce
cmddroid.c:62: warning: unused parameter ‘psBrainStats’
cmddroid.c:62: warning: unused parameter ‘player’
component.c:144: warning: unused parameter ‘CameraPos’
component.c:187: warning: unused parameter ‘psDroid’
component.c:193: warning: unused parameter ‘psDroid’
component.c:456: warning: unused parameter ‘Player’
data.c:145: warning: unused parameter ‘pData’
data.c:411: warning: unused parameter ‘pData’
data.c:454: warning: unused parameter ‘pData’
data.c:525: warning: unused parameter ‘pData’
data.c:549: warning: unused

[Warzone-dev] Bison warnings

2007-04-09 Thread Dennis Schridde 
There are quite a few bison warnings...

resource_parser.y: warning: conflicting outputs to file `resource_parser.tab.h'
strres_parser.y: warning: conflicting outputs to file `strres_parser.tab.h'
conflicts: 284 shift/reduce, 11 reduce/reduce
script_parser.y: warning: conflicting outputs to file `script_parser.tab.h'
chat_parser.y:234.8-11: warning: symbol _T_A redeclared
conflicts: 69 shift/reduce, 36 reduce/reduce
chat_parser.y: warning: conflicting outputs to file `chat_parser.tab.h'
conflicts: 284 shift/reduce, 11 reduce/reduce
chat_parser.y:234.8-11: warning: symbol _T_A redeclared
conflicts: 69 shift/reduce, 36 reduce/reduce
conflicts: 7 shift/reduce, 2 reduce/reduce
audp_parser.y:117.60: warning: rule never reduced because of conflicts: 
anim_file_list: /* empty */
audp_parser.y: warning: conflicting outputs to file `audp_parser.tab.h'
conflicts: 7 shift/reduce, 2 reduce/reduce
audp_parser.y:117.60: warning: rule never reduced because of conflicts: 
anim_file_list: /* empty */
conflicts: 4 shift/reduce
scriptvals_parser.y: warning: conflicting outputs to file 
`scriptvals_parser.tab.h'
conflicts: 4 shift/reduce


pgp1gsjEroyUW.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Dennis Schridde 
Am Montag, 9. April 2007 schrieb Per Inge Mathisen:
> On 4/9/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> > Well, why not remove the different debug modes at all then?
> > strict works pretty well atm so we could let it become yes and also merge
> > relaxed and no...
>
> We could/should merge "yes" and "strict"
done

> but "relaxed" adds -Wextra
Indeed. Maybe we could get the code extra clean and remove relaxed, too.

> and -O2 speed optimizations
It doesn't do that itself. This is autotool's default cflag.

> , and "no" adds -DNDEBUG and omits -g
-g comes with autotool's default cflags as well.
But "no" doesn't enforce it, yes.

> (and  should add -O3), IMHO.
IMHO it should not do that...
Optimization should be set by the distributor and not by us.
Actually we should only force those flags which are necessary and -O3 very 
certainly is not. It should be well known that -O3 brings very little to no 
performance improvements against -O2, but takes awefully much longer to 
compile and produces bigger binaries.
And type-punning warnings are allready produced by -O2...
And I doubt that many people will use -O3 when compiling or distributing 
binaries.

Again I strongly vote against forcing any unnecessary flags.

--Dennis


pgpshhnvjF7lF.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Per Inge Mathisen 
On 4/9/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> Well, why not remove the different debug modes at all then?
> strict works pretty well atm so we could let it become yes and also merge
> relaxed and no...

We could/should merge "yes" and "strict", but "relaxed" adds -Wextra
and -O2 speed optimizations, and "no" adds -DNDEBUG and omits -g (and
should add -O3), IMHO.

  - Per

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Dennis Schridde 
Am Montag, 9. April 2007 schrieb Per Inge Mathisen:
> On 4/9/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> > > >>>  * add -Werror-implicit-function-declaration to CFLAGS
> > > >
> > > > for debug=yes it is IMO not wanted, since yes!=strict.
>
> I dunno. I agree with Giel that linker errors are of the most annoying
> errors, because they appear so late (and in some environments -
> MacOSX, I am looking at you - they can be horribly hard to trace). So
> anything that makes them caught earlier is good.
Well, why not remove the different debug modes at all then?
strict works pretty well atm so we could let it become yes and also merge 
relaxed and no...

--Dennis


pgpK2cMgsKIWU.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Per Inge Mathisen 
On 4/9/07, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> > >>>  * add -Werror-implicit-function-declaration to CFLAGS
> > > for debug=yes it is IMO not wanted, since yes!=strict.

I dunno. I agree with Giel that linker errors are of the most annoying
errors, because they appear so late (and in some environments -
MacOSX, I am looking at you - they can be horribly hard to trace). So
anything that makes them caught earlier is good.

  - Per

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk : configure.ac makerules/configure.mk po/ po/da. po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Dennis Schridde 
Am Montag, 9. April 2007 schrieb Giel van Schijndel:
> Dennis Schridde schreef:
> > Am Montag, 9. April 2007 schrieb Dennis Schridde:
> >> Am Montag, 9. April 2007 schrieb Giel van Schijndel:
> >>> Author: muggenhor
> >>> Date: Mon Apr  9 17:02:04 2007
> >>> New Revision: 1048
> >>>
> >>> URL: http://svn.gna.org/viewcvs/warzone?rev=1048&view=rev
> >>> Log:
> >>>  * add -Werror-implicit-function-declaration to CFLAGS
> >>
> >> Quoting man:gcc
> >>
> >> -Werror-implicit-function-declaration
> >>  This warning is enabled by -Wall (as a warning, not an error).
> >>
> >> -Werror
> >>  Make all warnings into errors.
> >
> > So this is not needed for debug=strict. (Well, you didn't add it
> > there...) And for debug=yes it is IMO not wanted, since yes!=strict.
>
> Well, actually I did add it there on purpose (non-strict) since most
> implicit declarations later on simply result in linker errors (and
> linker errors are IMO difficult to trace).
Many things are difficult to trace. If we'd add them all, we'd end up 
with -Werror...

> And aside from that, implicit function declarations are (almost? can't
> think of any justified case at all) always very, very bad practice. So
> when considering that to be bad, one should not allow the compiler to
> accept it.
Sure they are bad practice. That's why you shouldn't commit patches which add 
new warnings.
To check that you can run with debug=strict. I don't see a reason why you 
should also add this to the warning mode.

> But then again, it's just my opinion that implicit function declarations
> are very bad.
You can always add custom CFLAGS by specifying
./configure CFLAGS='-Wwhatever'

But maybe others have a different opinion...

--Dennis


pgpuKf7lJX0cV.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Giel van Schijndel 
Dennis Schridde schreef:
> Am Montag, 9. April 2007 schrieb Dennis Schridde:
>   
>> Am Montag, 9. April 2007 schrieb Giel van Schijndel:
>> 
>>> Author: muggenhor
>>> Date: Mon Apr  9 17:02:04 2007
>>> New Revision: 1048
>>>
>>> URL: http://svn.gna.org/viewcvs/warzone?rev=1048&view=rev
>>> Log:
>>>  * add -Werror-implicit-function-declaration to CFLAGS
>>>   
>> Quoting man:gcc
>>
>> -Werror-implicit-function-declaration
>>  This warning is enabled by -Wall (as a warning, not an error).
>>
>> -Werror
>>  Make all warnings into errors.
>> 
> So this is not needed for debug=strict. (Well, you didn't add it there...)
> And for debug=yes it is IMO not wanted, since yes!=strict.
>   
Well, actually I did add it there on purpose (non-strict) since most
implicit declarations later on simply result in linker errors (and
linker errors are IMO difficult to trace).

And aside from that, implicit function declarations are (almost? can't
think of any justified case at all) always very, very bad practice. So
when considering that to be bad, one should not allow the compiler to
accept it.

But then again, it's just my opinion that implicit function declarations
are very bad.

-- 
Giel



signature.asc
Description: OpenPGP digital signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Dennis Schridde 
Am Montag, 9. April 2007 schrieb Dennis Schridde:
> Am Montag, 9. April 2007 schrieb Giel van Schijndel:
> > Author: muggenhor
> > Date: Mon Apr  9 17:02:04 2007
> > New Revision: 1048
> >
> > URL: http://svn.gna.org/viewcvs/warzone?rev=3D1048&view=3Drev
> > Log:
> >  * add -Werror-implicit-function-declaration to CFLAGS
>
> Quoting man:gcc
>
> -Werror-implicit-function-declaration
>  This warning is enabled by -Wall (as a warning, not an error).
>
> -Werror
>  Make all warnings into errors.
So this is not needed for debug=strict. (Well, you didn't add it there...)
And for debug=yes it is IMO not wanted, since yes!=strict.


pgpzGv8sjrk3X.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1048 - in /trunk: configure.ac makerules/configure.mk po/ po/da.po po/de.po po/nb.po po/nl.po src/droid.c

2007-04-09 Thread Dennis Schridde 
Am Montag, 9. April 2007 schrieb Giel van Schijndel:
> Author: muggenhor
> Date: Mon Apr  9 17:02:04 2007
> New Revision: 1048
>
> URL: http://svn.gna.org/viewcvs/warzone?rev=3D1048&view=3Drev
> Log:
>  * add -Werror-implicit-function-declaration to CFLAGS
Quoting man:gcc

-Werror-implicit-function-declaration
 This warning is enabled by -Wall (as a warning, not an error).

-Werror
 Make all warnings into errors.


pgp4OGTk4ddK0.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[Warzone-dev] Scripts to detect maybe dangerous GCC warnings.

2007-04-09 Thread Dennis Schridde 
This is ripped from Gentoo's QA section, slightly modified to run without the 
Portage library.

Maybe someone can unify them, so they can be added to SVN.

Usage:
make distclean && ./autogen.sh && ./configure --enable-debug && make 2> 
gcc_warnings.log && 
GCC_LOG_FILE=gcc_warnings.log ./gentoo_eval_gcc_warnings.sh


check-implicit-pointer-usage.py
Description: application/python


gentoo_eval_gcc_warnings.sh
Description: application/shellscript


pgpQLzpFIOIYF.pgp
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Fwd: Compilation error at generated resource_parser.tab.h]

2007-04-09 Thread Alejandro Pulver 
On Mon, 09 Apr 2007 13:36:19 +0200
Gerard Krol <[EMAIL PROTECTED]> wrote:

> Kamaze wrote:
> >  Original-Nachricht 
> > From: - Mon Apr 09 13:31:27 2007
> > Date: Sun, 8 Apr 2007 21:50:33 -0300
> > From: Alejandro Pulver <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Compilation error at generated resource_parser.tab.h
> > Mime-Version: 1.0
> > Content-Type: multipart/signed; 
> > boundary="Sig_fuYRTC9U2JBLiKWwDVejF=n"; 
> > protocol="application/pgp-signature"; micalg=PGP-SHA1
> >
> > Hello.
> >
> > I maintain the FreeBSD port (it's like a Gentoo .ebuild) of Warzone
> > 2100, and when I was updating it to the 2.0.6 version I got an error.
> >
> > The configure/make output and generated resource_parser.tab.h are
> > attached.
> >
> > If you need more information I will provide it.
> >
> > Do you know how to solve this?
> You need to use a more recent version of Bison. It seems that at least 
> version 2 is needed.
> Double check that you are invoking the correct version of Bison.
> Take a look at: http://wz2100.net/wiki/development:compile_guide_freebsd
> 

Thank you, I will commit the updated port after testing.

Best Regards,
Ale


signature.asc
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Fwd: Compilation error at generated resource_parser.tab.h]

2007-04-09 Thread Gerard Krol 
Kamaze wrote:
>  Original-Nachricht 
> From: - Mon Apr 09 13:31:27 2007
> Date: Sun, 8 Apr 2007 21:50:33 -0300
> From: Alejandro Pulver <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Compilation error at generated resource_parser.tab.h
> Mime-Version: 1.0
> Content-Type: multipart/signed; 
> boundary="Sig_fuYRTC9U2JBLiKWwDVejF=n"; 
> protocol="application/pgp-signature"; micalg=PGP-SHA1
>
> Hello.
>
> I maintain the FreeBSD port (it's like a Gentoo .ebuild) of Warzone
> 2100, and when I was updating it to the 2.0.6 version I got an error.
>
> The configure/make output and generated resource_parser.tab.h are
> attached.
>
> If you need more information I will provide it.
>
> Do you know how to solve this?
You need to use a more recent version of Bison. It seems that at least 
version 2 is needed.
Double check that you are invoking the correct version of Bison.
Take a look at: http://wz2100.net/wiki/development:compile_guide_freebsd

- Gerard

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Fwd: Compilation error at generated resource_parser.tab.h]

2007-04-09 Thread Giel van Schijndel 
Kamaze schreef:
>  Original-Nachricht 
> From: - Mon Apr 09 13:31:27 2007
> Date: Sun, 8 Apr 2007 21:50:33 -0300
> From: Alejandro Pulver <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Compilation error at generated resource_parser.tab.h
> Mime-Version: 1.0
> Content-Type: multipart/signed;
> boundary="Sig_fuYRTC9U2JBLiKWwDVejF=n";
> protocol="application/pgp-signature"; micalg=PGP-SHA1
>
> Hello.
>
> I maintain the FreeBSD port (it's like a Gentoo .ebuild) of Warzone
> 2100, and when I was updating it to the 2.0.6 version I got an error.
>
> The configure/make output and generated resource_parser.tab.h are
> attached.
>
> If you need more information I will provide it.
>
> Do you know how to solve this?
>
> Thanks and Best Regards,
> Ale
Looks like bison is spitting out some very bad code (or actually just
bloat, a line full of NUL chars).

-- 
Giel



signature.asc
Description: OpenPGP digital signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[Warzone-dev] [Fwd: Compilation error at generated resource_parser.tab.h]

2007-04-09 Thread Kamaze 



 Original-Nachricht 
From: - Mon Apr 09 13:31:27 2007
Date: Sun, 8 Apr 2007 21:50:33 -0300
From: Alejandro Pulver <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Compilation error at generated resource_parser.tab.h
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_fuYRTC9U2JBLiKWwDVejF=n"; 
protocol="application/pgp-signature"; micalg=PGP-SHA1


Hello.

I maintain the FreeBSD port (it's like a Gentoo .ebuild) of Warzone
2100, and when I was updating it to the 2.0.6 version I got an error.

The configure/make output and generated resource_parser.tab.h are
attached.

If you need more information I will provide it.

Do you know how to solve this?

Thanks and Best Regards,
Ale



make.log.bz2
Description: application/bzip


resource_parser.tab.h.bz2
Description: application/bzip


signature.asc
Description: PGP signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] [Warzone-commits] r1032 - in /trunk: lib/framework/ lib/netplay/ lib/sound/ src/

2007-04-09 Thread Gerard Krol 
Giel van Schijndel wrote:
> Gerard Krol schreef:
>   
>> Author: gerard_
>> Date: Sat Apr  7 15:23:14 2007
>> New Revision: 1032
>>
>> ...
>> 4. Commented out some unused sound code. I just love Valgrind :)
>> 
> There's no need to comment out code, in fact it probably is better to
> simply remove it. If we or anyone ever need that code back, then
> Subversion can retrieve it.
>
> Reverse difference merging of a revision can do it for example: `svn
> merge -r500:499` will reverse all changes made in revision 500 and apply
> them to your local working copy. So as long as you make a note of what
> it is you removed in your commit log it should be fine.
>
> Cluttering the codebase with commented out code probably is worse than
> ever needing to track down a revision in which some part of code was
> removed.
>   
Fine, I'll remove it then.
> Plus your way of commenting out code (#if 0;#endif) isn't very easy to
> spot and recognize as disabled code.
>   
This is the recommended way to comment out code though. /* */ don't 
properly nest.

- Gerard

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[Warzone-dev] [bug #8895] The reloading state of static long range weapons gets lost in savegame

2007-04-09 Thread anonymous 

URL:
  

 Summary: The reloading state of static long range weapons
gets lost in savegame
 Project: Warzone Resurrection Project
Submitted by: None
Submitted on: Montag 09.04.2007 um 10:22 CEST
Category: Engine: Scripting
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Assigned to: None
Originator Email: [EMAIL PROTECTED]
 Open/Closed: Open
 Discussion Lock: Any
 Release: 2.0.6_pre
Operating System: Microsoft Windows

___

Details:

This means after loading a game all static long range weapons start to fire
together as if thery have never been fireing before and as if they were all
build together at exactly the same time.




___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Gna!
  http://gna.org/


___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[Warzone-dev] [bug #8894] Can´t llink VTOL to sensor tower wich was taken via Nexus link turret before

2007-04-09 Thread anonymous 

URL:
  

 Summary: Can´t llink VTOL to sensor tower wich was taken
via Nexus link turret before
 Project: Warzone Resurrection Project
Submitted by: None
Submitted on: Montag 09.04.2007 um 10:18 CEST
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Assigned to: None
Originator Email: [EMAIL PROTECTED]
 Open/Closed: Open
 Discussion Lock: Any
 Release: 2.0.6_pre
Operating System: Microsoft Windows

___

Details:

I can´t link my VTOL to a sensor tower wich was overtaken by my mobile nexus
link turret before.




___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Gna!
  http://gna.org/


___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev