[Solved] Problem compiling with makedevenv-5

[rumi]

Hello,

basically Ubuntu 8.04 amd64, vdr 1.6.0 from e-tobi.

I got with makedevenv-5 after many minutes

Code Select Expand

/usr/local/src/crosstool/gcc-3.4.5-glibc-2.2.5/powerpc-405-linux-gnu/bin/powerpc-405-linux-gnu-g++ -O3 -Wall -Wshadow -Werror -D_GNU_SOURCE -I../jpeg/jpeg-6b   -c -o vdr.o vdr.cc
vdr.cc: In member function `virtual void VDR::threadMethod()':
vdr.cc:197: warning: 'vresp' might be used uninitialized in this function
make: *** [vdr.o] Fehler 1
What's wrong ?

is asking rumi

[muellerph]

It's the newer GCC together with the setting that warning should be treated as errors.

At least this is the explanation for the error, but I have no detailed analysis what needs to be changed in order to avoid it.

[rumi]

But I'm thinking makedevenv-5 use the gcc-3.4.5 with the crosstool.

[rumi]

OḰ ... it works.

First I tried on my old machine with Ubuntu 7.10 ... works fine.

Then I tried it a second time on my new VDR-Server ... I don't know why, but now itworks also.

Thanks in advance

rumi

[Chris]

Hi, this is also partly because the makedevenv script pulls in the code for vompclient from CVS which is constantly changing at the moment in the run up to the next release. And by the way - cvs vomp is not really suitable for proper use on a production VDR - it has the potential to lock up receivers in the server.

If you really want to use cvs vomp at the moment just make sure you don't kill the power to the mvp whilst watching live tv - exit live tv cleanly.

[svalavuo]

My Fedora9 says:

Code Select Expand


checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for pwd... /bin/pwd
checking build system type... i686-pc-linux-gnu
checking for powerpc-405-linux-gnu-gcc... gcc
checking version of gcc... 4.3.0, bad
checking for gnumake... no
checking for gmake... gmake
checking version of gmake... 3.81, ok
configure: error:
*** These critical programs are missing or too old:gcc
*** Check the INSTALL file for required versions.

How come 4.3.0 is bad and/or old?

Samuli

[davep]

How come 4.3.0 is bad and/or old?

We've been here before.

http://www.loggytronic.com/forum/index.php?topic=229.msg1348#msg1348