Alan McKinnon <alan.mckin...@gmail.com> [12-02-18 16:00]: > On Sat, 18 Feb 2012 15:37:24 +0100 > Alex Schuster <wo...@wonkology.org> wrote: > > > meino.cra...@gmx.de writes: > > > > > As this line in my previous posting states, museseq needs Qt 4.*, > > > which is installed...: > > > > > > configure: error: need qt >= 3.2.0 > > > > Um, huh? If it would need Qt 4.*, it would say that you need qt >= > > 4.something. But it says you need qt >= 3.2.0, so qt-meta 3.3.8b-r2 > > (which I have installed) would do fine. > > Oh, I just see that this is no longer in portage, my qt-meta:3 comes > > from the kde-sunset overlay. > > > > Maybe having Qt4 installed with the qt3support USE flag would work, > > but I doubt it. Qt4 is very different from Qt3. > > my understanding is that qt3support gives run-time support only > for apps built against qt3 but running under qt4 (i.e it's just a > simple run-time wrapper around API calls). > > But qt3support cannot be used to built against qt4 > > -- > Alan McKinnnon > alan.mckin...@gmail.com > >
So, if QT3 is removed from protage, and museseq which still is in portage seems only to build agains qt3, I see a contradiction here... May be on my system there somewhere leftovers from ancient time, when qt3 needs some additional environment variables or such (?)... what would it be...where I can I look for such settings? best regards, mcc
