Rivatv problem, can't make!

[Why me]

I can not get this stupid thing to work no matter what I do!
What am I missing here??
Thanks!!

[jim@localhost rivatv-0.8.2]$ ./configure --with-kernel=/usr/src/linux-2.4.20-2mdk

Checking for configured kernel headers... found [/usr/src/linux-2.4.20-2mdk]
Checking for linux kernel >= 2.4.0... yes [2.4.20-2mdksmp
2.4.20-2mdkenterprise
2.4.20-2mdk
2.4.20-2mdksecure]
Checking for kernel build system... found
Checking for kernel configuration... found
Checking for CONFIG_MODVERSIONS... yes
Checking for CONFIG_PCI... yes [y]
Checking for CONFIG_VIDEO_DEV... yes [m]
Checking for CONFIG_PROC_FS... yes [y]
Checking for CONFIG_I2C... yes [m]
Checking for CONFIG_I2C_ALGOBIT... yes [m]
Creating Makefile... sed: -e expression #1, char 71: Unterminated `s' command
done
Checking your current setup for incompatibilities...
Checking for /proc... yes
Checking for framebuffer... no
Checking for SMP... no

No problems found.
To build RivaTV type `make'. For cleaning up type `make clean`.

[jim@localhost rivatv-0.8.2]$ make
make: *** No targets. Stop.

Thanks!!:confused: :(

[bwkaz]

Are you using SMP, the enterprise kernel features, or the "secure" kernel features? If not, get rid of those kernels.

The unterminated sed command could be anything, but my first idea is that the sed command is actually terminated, just on a different line than sed expects, so it complains. And I think it might be set this way because of the way the "checking for linux kernel >= 2.4.20" status got printed -- on multiple lines, one for (presumably) each kernel you have installed. Perhaps getting rid of the extraneous kernels that you don't use will help.

If that doesn't help, then you're going to have to open the configure script up and search for "Creating Makefile", then look for the next few calls of sed. The sed executable doesn't like one of them, but there's no way of telling which one without seeing the script. Maybe I can pull it down in the near future and see if I can see anything obvious.

[Why me]

Originally posted by bwkaz
Are you using SMP, the enterprise kernel features, or the "secure" kernel features? If not, get rid of those kernels.

The unterminated sed command could be anything, but my first idea is that the sed command is actually terminated, just on a different line than sed expects, so it complains. And I think it might be set this way because of the way the "checking for linux kernel >= 2.4.20" status got printed -- on multiple lines, one for (presumably) each kernel you have installed. Perhaps getting rid of the extraneous kernels that you don't use will help.

If that doesn't help, then you're going to have to open the configure script up and search for "Creating Makefile", then look for the next few calls of sed. The sed executable doesn't like one of them, but there's no way of telling which one without seeing the script. Maybe I can pull it down in the near future and see if I can see anything obvious.

Hi,

No, I'm just using the 2.4.20-2mdk kernel, I have no idea what those other kernels are being listed for and I had no idea they were present on my machine????
Where would I look for them to move or delete them???

Thanks!

[bwkaz]

Go into Software Manager (it'll probably prompt for your root password), and search for "smp" in the "packages currently installed". Remove the kernel by checking the box and hitting whatever button it is. Repeat for "enterprise" and "secure". Make sure you only remove the kernels, though (some other stuff might have "smp" in the name, for example; it should stay).