Re: QT on alpha potato does not compile
It seems that trying to compile designer without having qt2.2 already
installed causes uic not to be able to find libqutil (since it hasn't been
installed yet and isn't preloaded). Designer really should be a different
source package anyway, IMO, which I'm going to recommend, especially since
it requires qt2.2 to be installed before compiling (a build dependency on
itself if it remains lumped in with the qt2.2 source package).
I'm cc'ing the maintainer in hopes that we can resolve this without filing
a bug at this time.
On Thu, 7 Sep 2000, Christopher C. Chimelis wrote:
> Looks like i spoke too soon. The qt2.2-2.2.0-20000906 package that was
> installed into master today dies during compile (despite working around
> the optimiser bug...there's something going wrong with the build procedure
> I believe). I'll be filing a bug against qt2.2 once I figure out what's
> going on exactly, but I'll leave the gcc bug filing to you.
> On Thu, 7 Sep 2000, Ullrich Martini wrote:
> > I am trying to compile qt 2.2 on a alpha with potato, g++ 2.95.2-13
> > using rkrustys patches from the
> > intel qt 2.2 diffs. I get lots of internal compiler errors on the files
> > generated by moc (moc_*.cpp), and
> > uic segfaults when compiling tools/designer/designer/listboxeditor.ui
> > It looks like a alpha-gcc problem. The internal compiler errors go away
> > if the files
> > are compiled without optimization. I will file a bug against gcc because
> > of that.
> > The uic problem occurred when building the designer. I think the Qt
> > designer should go into
> > a separate package anyway.
> > The kde people had similiar bugs against kde2 betas in their bugtracking
> > system, but they closed them because they had a modified version of qt
> > which appearently fixed the problems. It looks like those patches didn't
> > find their way back to the trolls.
> > Anyway, did someone succeed in building qt-2.2 on a alpha/potato?
> > thanks, Ullrich
> > --
> > To UNSUBSCRIBE, email to email@example.com
> > with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
> To UNSUBSCRIBE, email to email@example.com
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org