gmfsk compile

gmfsk compile

[richard]

Hi guys
can anyone throw some light on this compile failure.
gcc-4.0.1, kernel-2.6.12-14mdk, mandriva 2006CE, FFTW 2.1.5 and fftw3( needed for other apps)
gmsk-0.6,hamlibs 1.2.4 + devel

dsp.h: In function 'void LowPass2(typeInp, LowPass2elem&, typeW, typeW, typeW)':
dsp.h:558: error: 'Out' was not declared in this scope
dsp.h: In function 'void LowPass2(typeInp, LowPass2elem&, LowPass2weight&)':
dsp.h:565: error: 'Weigth' was not declared in this scope
dsp.h:566: error: 'Out' was not declared in this scope
make[3]: *** [dsp.o] Error 1
make[3]: Leaving directory `/home/richard/HamApps/gmfsk-0.6/src/mt63'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/richard/HamApps/gmfsk-0.6/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/richard/HamApps/gmfsk-0.6'
make: *** [all] Error 2


tnx
Richard g8jvm

Re: gmfsk compile

[Curt Mills]

On Sat, 7 Jan 2006, richard wrote:

> Hi guys
> can anyone throw some light on this compile failure.
> gcc-4.0.1, kernel-2.6.12-14mdk, mandriva 2006CE, FFTW 2.1.5 and fftw3( needed
> for other apps)
> gmsk-0.6,hamlibs 1.2.4 + devel

It's GCC-4 that's doing it to you.  It enforces stricter compliance
with the C specs.

You'd need to go back to the developers and have them change the
code so that it was in compliance with what GCC-4 expects.  We had
to do that for the Xastir project because defining functions inside
functions isn't allowed in GCC-4.x.

-- 
Curt, WE7U.				archer at eskimo dot com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"

Re: gmfsk compile

[richard]

Curt Mills wrote:
> On Sat, 7 Jan 2006, richard wrote:
> 
> 
>>Hi guys
>>can anyone throw some light on this compile failure.
>>gcc-4.0.1, kernel-2.6.12-14mdk, mandriva 2006CE, FFTW 2.1.5 and fftw3( needed
>>for other apps)
>>gmsk-0.6,hamlibs 1.2.4 + devel
> 
> 
> It's GCC-4 that's doing it to you.  It enforces stricter compliance
> with the C specs.
> 
> You'd need to go back to the developers and have them change the
> code so that it was in compliance with what GCC-4 expects.  We had
> to do that for the Xastir project because defining functions inside
> functions isn't allowed in GCC-4.x.
> 
Thanks Curt, I thought something like that, but found a patch for dsp.h that allowed it to compile
on this computer, but alsa not my friends.

his compile fails at
/usr/include/pango-1.0/pango/pangocairo.h:66: warning: type defaults to
'int' in declaration of 'cairo_font_options_t'
/usr/include/pango-1.0/pango/pangocairo.h:66: error: syntax error before
'*' token
/usr/include/pango-1.0/pango/pangocairo.h:67: error: syntax error before
'*' token
/usr/include/pango-1.0/pango/pangocairo.h:67: warning: type defaults to
'int' in declaration of 'pango_cairo_context_get_font_options'
/usr/include/pango-1.0/pango/pangocairo.h:67: warning: data definition
has no type or storage class
In file included from /usr/include/gtk-2.0/gdk/gdk.h:50,
                  from /usr/include/gtk-2.0/gtk/gtk.h:31,
                  from /usr/include/libgnomeui-2.0/gnome.h:4,
                  from ../../src/main.h:32,
                  from mfsktx.c:42:
/usr/include/gtk-2.0/gdk/gdkscreen.h:51: error: syntax error before
'cairo_font_options_t'
/usr/include/gtk-2.0/gdk/gdkscreen.h:51: warning: no semicolon at end of
struct or union
/usr/include/gtk-2.0/gdk/gdkscreen.h:53: error: syntax error before '}'
token
/usr/include/gtk-2.0/gdk/gdkscreen.h:106: warning: type defaults to
'int' in declaration of 'cairo_font_options_t'
/usr/include/gtk-2.0/gdk/gdkscreen.h:106: error: syntax error before '*'
token
/usr/include/gtk-2.0/gdk/gdkscreen.h:107: error: syntax error before '*'
token
/usr/include/gtk-2.0/gdk/gdkscreen.h:107: warning: type defaults to
'int' in declaration of 'gdk_screen_get_font_options_libgtk_only'
/usr/include/gtk-2.0/gdk/gdkscreen.h:107: warning: data definition has
no type or storage class
mfsktx.c: In function 'sendchar':
mfsktx.c:118: warning: pointer targets in initialization differ in
signedness
mfsktx.c: In function 'mfsk_txprocess':
mfsktx.c:314: warning: pointer targets in assignment differ in signedness
mfsktx.c:315: warning: pointer targets in passing argument 1 of
'statusbar_set_main' differ in signedness
make[2]: *** [mfsktx.o] Error 1
make[2]: Leaving directory `/home/g8bhh/HamApps/gmfsk-0.6/src/mfsk'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/g8bhh/HamApps/gmfsk-0.6/src'
make: *** [check-recursive] Error 1

Thanks
Richard

Re: gmfsk compile

[Tomi Manninen]

On Sat, 2006-01-07 at 16:10, richard wrote:

> gmsk-0.6

> dsp.h: In function 'void LowPass2(typeInp, LowPass2elem&, typeW, typeW, typeW)':
> dsp.h:558: error: 'Out' was not declared in this scope
> dsp.h: In function 'void LowPass2(typeInp, LowPass2elem&, LowPass2weight&)':
> dsp.h:565: error: 'Weigth' was not declared in this scope
> dsp.h:566: error: 'Out' was not declared in this scope
> make[3]: *** [dsp.o] Error 1
> make[3]: Leaving directory `/home/richard/HamApps/gmfsk-0.6/src/mt63'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/richard/HamApps/gmfsk-0.6/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/richard/HamApps/gmfsk-0.6'
> make: *** [all] Error 2

This is a bug in the MT63 code (*). It's fixed in 0.7pre1 which I would 
recommend for everyone. From the feedback it seems 0.7pre1 is just as
stable as 0.6 if not better. And you get a few new goodies with it.
Go to http://gmfsk.connect.fi/ to get it.

/Tomi

*) Yes, it's compiler dependent but I think it was somewhere around
GCC 3.4 when this became visible...

-- 
Tomi Manninen / OH2BNS / KP20JF74