Compiling problem with Linrad 0104 in Mandrake 9.1

["Ramiro Aceves, EA1ABZ" <ea1abz@xxxxxxxxxxxxxx]

Leif Asbrink wrote:

All right.

I have just installed 0104 version in the 486 mandrake 6.1 and it
works(I goes very smooth with fft2 disabled, but when I set ftt2 on 
svgalib gets a "segmentation fault reveived") but I CAN NOT compile it in
the Mandrake 9.1 with the athlon.

I get the following error at the beginning of the compiling session,
when compiling uivar.c file:

[root@xxxxxxxxx linrad-01.04]# make
gcc -O -W -Wimplicit -Wreturn-type -Wformat \
-Wunused -Wcomment -Wchar-subscripts -Wshadow -Wuninitialized \
-Wparentheses -Wstrict-prototypes -Werror -ffast-math -fforce-mem \
-fomit-frame-pointer -c -o main.o \
main.c
gcc -O -W -Wimplicit -Wreturn-type -Wformat \
-Wunused -Wcomment -Wchar-subscripts -Wshadow -Wuninitialized \
-Wparentheses -Wstrict-prototypes -Werror -ffast-math -fforce-mem \
-fomit-frame-pointer -c -o ui.o \
ui.c
gcc -O -W -Wimplicit -Wreturn-type -Wformat \
-Wunused -Wcomment -Wchar-subscripts -Wshadow -Wuninitialized \
-Wparentheses -Wstrict-prototypes -Werror -ffast-math -fforce-mem \
-fomit-frame-pointer -c -o setvga.o \
setvga.c
gcc -O -W -Wimplicit -Wreturn-type -Wformat \
-Wunused -Wcomment -Wchar-subscripts -Wshadow -Wuninitialized \
-Wparentheses -Wstrict-prototypes -Werror -ffast-math -fforce-mem \
-fomit-frame-pointer -c -o uivar.o \
uivar.c
cc1: warnings being treated as errors
uivar.c:334: warning: excess elements in array initializer
uivar.c:334: warning: (near initialization for `cg_floatpar_text')
uivar.c:343: warning: excess elements in array initializer
uivar.c:343: warning: (near initialization for `eg_floatpar_text')
make: *** [uivar.o] Error 1
[root@xxxxxxxxx linrad-01.04]#


I like this new version, I like the new waterfall and the parameters
config included in the graph, saving space on the screen.
I'll tell you more new as I play enough with all versions.


73, Ramiro

> I am very interested to know if there is any noticeable
> performance difference between the versions. Try to
> decrease bandwidth and try inefficient screen operations
> (large waterfall or very small averaging numbers together
> with small fft sizes) until you reach the performance limit
> where it does not work any longer. I am very interested to
> know if there is a significant difference between versions.
>
> I am also interested to know how far you can get on a 486.
> Linrad-01.04 has a qrss mode that might allow very narrow
> filters, 0.01 Hz or so on a 486. Does it work or not?
>
> Any observation of unexpected behaviour is interesting.
>
>
> 73
>
> Leif







LINRADDARNIL