Re: [Gwc-general] another case of problems compiling gwc-0.19-5

[John C. <ci...@pu...>]

Howard,

I see. I added the {} in gwc.c and then got by with only a couple 
of minor errors. Then got the error in audio_util.c. I added the 
{} there too, and the next thing was a series of errors in 
encode.c, which I likewise fixed with the {}. Strangely it went on 
and completed the rest of the files. I didn't get the gtk.h not 
found error, it just finished! I ran ./gwc and it came up. I 
haven't used it yet because it's getting way late. I'll try it 
over the weekend.
I have gtk 1.2 and 2.0 installed, if that makes a difference. Both 
include a gtk.h file.

Good Luck,

John Cirillo

Howard Sanner wrote:
> John Cirillo wrote:
> 
>> I know you love getting these. I can't tell what is failing this time. 
>> gwc-0.19-2 still compiles fine, and also gwc-0.19-3 with the minor mod 
>> I reported a few months ago. But gwc-0.19-5 just pukes when it hits 
>> gwc.c. Here is what it complains about:
>>
>> [jcirillo@john1 gwc-0.19-5]$ make
>> cc -O3 -Wall -DHAVE_FFTW -mcpu=i686 -march=i686 `gnome-config --cflags 
>> gnome gnomeui`   -c -o gwc.o gwc.c
>> gwc.c: In function `estimate':
>> gwc.c:508: parse error before `long'
>> gwc.c:509: `first' undeclared (first use in this function)
>> gwc.c:509: (Each undeclared identifier is reported only once
>> gwc.c:509: for each function it appears in.)
>> gwc.c:509: `last' undeclared (first use in this function)
> 
> 
> 
>     This is the problem I mentioned.
> 
>     The blocks in which these variables are declared need to be enclosed 
> in a set of {}. Put a { before long and put a } at the end of the block. 
> Continue likewise for all the errors listed.
> 
>     When you get done, gwc.c will compile clean, but you'll get the same 
> kinds of error messages (just fewer of them!) for audio_util.c. Fix 
> audio_util.c in the same manner. After that is when I get the gtk.h not 
> found error, and at that point I gave up.
> 
>     It is nice to know that I'm not the only one having troubles, though.
> 
>                     Howard Sanner
>                     fla...@mi...
> 
>