[kde-freebsd] qt upgrade strangeness

[John Nielsen]

On Tuesday 17 April 2007 10:01:56 am Michael Nottebrock wrote:
> On Monday, 16. April 2007, Andy Fawcett wrote:
> > Hi,
> >
> > > -----Original Message-----
> > > From: John Nielsen [mailto:lists at jnielsen.net]
> > > Sent: Thursday, April 05, 2007 19:32
> > > To: kde at freebsd.org
> > > Cc: x11 at freebsd.org
> > > Subject: Re: [kde-freebsd] qt upgrade strangeness
> > >
> > > On Thursday 05 April 2007 12:29:27 pm John Nielsen wrote:
> > > > I've had some trouble upgrading qt on two different machines now. I'm
> > >
> > > using
> > >
> > > > the experimental Xorg git ports tree on both and I'm not sure if
> > > > that's
> > >
> > > a
> > >
> > > > factor, which is why I'm CC-ing x11 at .
> > > >
> > > > In short, qt will install happily the first time but not the second.
> > > > It looks to my untrained eye like building [an upgraded] qt when qt
> > > > is
> > >
> > > already
> > >
> > > > installed somehow taints the build. The build will complete
> > >
> > > successfully,
> > >
> > > > but it will fail during the install step whether or not the old qt
> > > > was uninstalled between the make and install steps--I tried an
> > > > install
> > >
> > > without
> > >
> > > > uninstalling the old one using FORCE_PKG_REGISTER and it failed
> > > > differently, but it still failed. However, if qt and qmake are
> > > > removed completely before starting the [new] build for qt, it will
> > > > install just fine.
> > > >
> > > > I'd like to determine if 1) this is a known problem and 2) this is
> > >
> > > specific
> > >
> > > > to the Xorg ports tree so I know whether or not to send in a PR.
> > >
> > > I forgot to mention this was during an attempt to update qt from
> > > qt-copy- 3.3.8
> > > to qt-copy-3.3.8_1 on a 7-CURRENT (as of several days ago) box. I also
> > > saw the problem on a previous qt upgrade on a machine running 6-STABLE
> > > several weeks ago.
> >
> > Originally I reported that I wasn't seeing this.
> >
> > Now, I've just updated to the very latest git X11 ports, with X11BASE
> > migrated to LOCALBASE, and get this problem.
> >
> > cd src/moc && make
> > cd src/moc && make install
> > cp -f "../../bin/moc" "/usr/local/bin/moc"
> > cd src && make
> > make: don't know how to make /usr/local/include/qconfig.h. Stop
> > *** Error code 2
> >
> >
> > Quite weird, I've never seen this before.
>
> I dimly remember seeing that before - I don't think Qt/qmake can actually
> handle a PREFIX-move cleanly and once the prefix has changed, it has to be
> deinstalled *before* rebuilding it, or else this will happen.

Just to clarify, I'm seeing the brokenness on machines where I deinstalled ALL 
ports, changed X11BASE in /etc/make.conf, and reinstalled using ONLY the git 
ports tree. The first installation of qt is fine. Attempting to upgrade ONLY 
qt with no PREFIX changes and no other major upgrades still fails. Bumping 
portrevision on qmake and/or qt won't help; in fact it's the last couple 
bumps (including one for qt I saw yesterday) that have preceeded the failed 
upgrade attempts.

It may well be that something in qt is not X11BASE-clean, but blaming the 
breakage on a major upgrade or system layout change will not result in a 
useful fix being created.

A failed qt upgrade fails partway through the "make install" target, so the 
port is no longer registered but some files from the new version are on the 
system. My workaround is to reinstall from the backup package created by 
portupgrade, manually force-uninstall qt and qmake (to get ride of the 
partial installation), remove any existing work directories and then do 
a "make install" for x11/qt33. It works fine at that point.

JN