Hallo zusammen,
nach dem Upgrade von Woody nach Sarge kann ich zum Verrecken den VDR nicht mehr kompilieren, /usr/include ist offenbar vermasselt.
Ich erhalte massig Meldungen wie diese:
config.o(.text+0x3798):/usr/include/stdlib.h:302: undefined reference to `__throw' config.o(.text+0x37a1):/usr/include/stdlib.h:303: undefined reference to `__start_cp_handler'
DVB-Treiber, Kernel 2.4.31, etc. läßt sich wunderbar kompilieren, ich hab jetzt gcc-3.3 aber mein /usr/include ist scheinbar "versaut".
Frage: wie kann ich das geradebiegen, daß VDR wieder kompiliert?
TIA Frederick
I demand that Frederick Page may or may not have written...
Hallo zusammen,
nach dem Upgrade von Woody nach Sarge kann ich zum Verrecken den VDR nicht mehr kompilieren, /usr/include ist offenbar vermasselt.
[snip]
Could you repost this in English?
Moin,
[in englisch, please] -------------- After upgrading from Woody to Sarge i can't compile vdr any more. /usr/include is apparently messed.
I got many messages as these:
config.o(.text+0x3798):/usr/include/stdlib.h:302: undefined reference to `__throw' config.o(.text+0x37a1):/usr/include/stdlib.h:303: undefined reference to `__start_cp_handler'
DVB-Driver, Kernel 2.4.31, etc. compiles flawlessley. I'am using gcc-3.3 now, but my /usr/include seemed to be [MEEP!].
How can i fix this mess and compile vdr without error. ---------------
(Translator's note: i can compile it without a flaw (Sarge, 1.3.22 and 1.3.27) )
Gruss, Walter
Hi Walter,
Walter Koch wrote on Thu, Jun 30 2005:
I got many messages as these:
config.o(.text+0x3798):/usr/include/stdlib.h:302: undefined reference to `__throw'
(Translator's note: i can compile it without a flaw (Sarge, 1.3.22 and 1.3.27) )
So can I now, if I had not been THAT darn stupid. Please look above: config.o (an object!) gave the errors. Considering that I upgraded from Woody to Sarge (meaning libc6 and gcc), it's not a big surprise that I could not compile with the old (stale!) objects.
A simple "make clean" did the trick. I am truly sorry about this stupid question of mine, of course everything works fine.
Best regards Frederick
I demand that Frederick Page may or may not have written...
Walter Koch wrote on Thu, Jun 30 2005:
I got many messages as these: config.o(.text+0x3798):/usr/include/stdlib.h:302: undefined reference to `__throw'
(Translator's note: I can compile it without a flaw (Sarge, 1.3.22 and 1.3.27) )
So can I now, if I had not been THAT darn stupid. Please look above: config.o (an object!) gave the errors.
Hmm, yes. I've been running sarge for quite some time now, so it's little wonder that I didn't spot that :-\
Considering that I upgraded from Woody to Sarge (meaning libc6 and gcc), it's not a big surprise that I could not compile with the old (stale!) objects.
The same will happen when you (eventually) upgrade to etch - there's another C++ transition on the way.
A simple "make clean" did the trick. I am truly sorry about this stupid question of mine, of course everything works fine.
You could use my packages or the official Debian vdr package in unstable; if you're using xine-lib, it'd be better to use my packages since vdr-plugin-xine isn't in unstable (and probably won't be until after xine-lib is appropriately patched).
-
Darren Salt -
Frederick Page -
Walter Koch