| 1 |
Alan McKinnon <alan.mckinnon@×××××.com> [12-02-18 16:00]: |
| 2 |
> On Sat, 18 Feb 2012 15:37:24 +0100 |
| 3 |
> Alex Schuster <wonko@×××××××××.org> wrote: |
| 4 |
> |
| 5 |
> > meino.cramer@×××.de writes: |
| 6 |
> > |
| 7 |
> > > As this line in my previous posting states, museseq needs Qt 4.*, |
| 8 |
> > > which is installed...: |
| 9 |
> > > |
| 10 |
> > > configure: error: need qt >= 3.2.0 |
| 11 |
> > |
| 12 |
> > Um, huh? If it would need Qt 4.*, it would say that you need qt >= |
| 13 |
> > 4.something. But it says you need qt >= 3.2.0, so qt-meta 3.3.8b-r2 |
| 14 |
> > (which I have installed) would do fine. |
| 15 |
> > Oh, I just see that this is no longer in portage, my qt-meta:3 comes |
| 16 |
> > from the kde-sunset overlay. |
| 17 |
> > |
| 18 |
> > Maybe having Qt4 installed with the qt3support USE flag would work, |
| 19 |
> > but I doubt it. Qt4 is very different from Qt3. |
| 20 |
> |
| 21 |
> my understanding is that qt3support gives run-time support only |
| 22 |
> for apps built against qt3 but running under qt4 (i.e it's just a |
| 23 |
> simple run-time wrapper around API calls). |
| 24 |
> |
| 25 |
> But qt3support cannot be used to built against qt4 |
| 26 |
> |
| 27 |
> -- |
| 28 |
> Alan McKinnnon |
| 29 |
> alan.mckinnon@×××××.com |
| 30 |
> |
| 31 |
> |
| 32 |
|
| 33 |
So, if QT3 is removed from protage, and museseq which still is in |
| 34 |
portage seems only to build agains qt3, I see a contradiction here... |
| 35 |
|
| 36 |
May be on my system there somewhere leftovers from ancient time, |
| 37 |
when qt3 needs some additional environment variables or such (?)... |
| 38 |
what would it be...where I can I look for such settings? |
| 39 |
|
| 40 |
best regards, |
| 41 |
mcc |
Archives