Re: dvb.o: unresolved symbol memset

[Frank Verlinden <fverlind@tref.nl>]

Thilo,
I had the same problem.
Change your gcc version to 2.95.2 and it will work.

succes,
Frank.

Thilo Wunderlich wrote:

> I´m trying to compile and run 0.04:
> Compiling is ok but
> make[1]: Leaving directory `/usr/src/sat/DVB/driver'
> (       \
> insmod i2c-core.o; \
> insmod videodev.o;              \
> insmod saa7146_core.o mode=0;   \
> insmod saa7146_v4l.o;           \
> insmod VES1893.o;               \
> insmod VES1820.o;               \
> insmod dvb.o;                   \
> insmod tuner.o;                 \
> insmod msp3400.o;               \
> ifconfig dvb0 192.168.4.1;      \
> )
> dvb.o: unresolved symbol memset
> msp3400.o: unresolved symbol unregister_sound_mixer_R7afc9d8a
> msp3400.o: unresolved symbol register_sound_mixer_R54848dd0
> SIOCSIFADDR: Operation not supported by device
> dvb0: unknown interface: Operation not supported by device
> make: *** [insmod] Error 255
>
> dmesg shows:
> i2c-core.o: i2c core module
> Linux video capture interface: v1.00
> saa7146_core.o: saa7146(1): bus:0, rev:1, mem:0xd081c000.
> saa7146_core.o: 1 saa7146 chipset(s) found.
> VES1893: attaching VES1893 at 0x10
> VES1893: init chip
> VES1893: attached to adapter saa7146(1)
> VES1893: init_module
> VES1820: init_module
> tuner: chip found @ 0x61
>
> When using 0.039 I get the same error but without the msp3400 part.
>
> This is a Technotrend card with Linux 2.2.14
>
> Any ideas ?
>
> Thilo
>
> PS: could you guys please add a revision number to the dir in the
> tar file, e.g. DVB-0.04. So it is easier to distinguish different
> versions.
>
> --
> Thilo Wunderlich     thilo@speedway.org     www.speedway.org