Arttu V. wrote: > On 4/8/09, Dale <rdalek1...@gmail.com> wrote: > >> Anybody ran into this: >> > <snip/> > >>> Selector.cxx: In constructor 'Selector::Selector(QWidget*)': >>> Selector.cxx:125: error: '::getenv' has not been declared >>> > <snip/> > >> I searched the forums but it returned very little and most of that was >> really really old. I went back a good piece and I think all the error >> should be there but if I missed something, let me know. I can go back a >> little further if needed. >> > > Ok, the gurus won't touch this (at least on list) so I'll throw out a > wild guess: maybe a gcc 4.3 related issue in kbackup 0.5.3's sources? > > If kbackup 0.5.4[-r1] (currently ~arch) has the same then you probably > want to file a bug about it at b.g.o. Otherwise a bug report will just > be a waste of time, it'll get either ignored or closed with a > suggestion to use the newer one. (I.e., then one must try to > out-clever the devs and file a stabilization bug for the newer one? ;) > ) > >
I have the same thing for both Kbackup and hwinfo. It looks like it is a boo boo between the kernel and gcc. I'm no guru but it appears that gcc is looking for something in one place but the new kernels are putting it somewhere else. It's on google so they know about this. Just wish people would share a little more is all. That was my take at least. I'm using kbackup-0.5.3 and kde-3.5.10 if that matters any. Dale :-) :-)
