Date: Tue, 17 Apr 2007 20:58:42 +0200 From: Michael Nottebrock <lofi@freebsd.org> To: Dejan Lesjak <dejan.lesjak@ijs.si> Cc: freebsd-x11@freebsd.org, Andy Fawcett <andy@athame.co.uk>, kde@freebsd.org Subject: Re: [kde-freebsd] qt upgrade strangeness Message-ID: <200704172058.53674.lofi@freebsd.org> In-Reply-To: <200704171638.39985.dejan.lesjak@ijs.si> References: <200704051229.27994.lists@jnielsen.net> <200704171633.59007.lofi@freebsd.org> <200704171638.39985.dejan.lesjak@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart51220347.OT21hAQaud Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday, 17. April 2007, Dejan Lesjak wrote: > On Tuesday 17 of April 2007, Michael Nottebrock wrote: > > On Tuesday, 17. April 2007, Michael Nottebrock wrote: > > > On Monday, 16. April 2007, Andy Fawcett wrote: > > > > Hi, > > > > > > > > > -----Original Message----- > > > > > From: John Nielsen [mailto:lists@jnielsen.net] > > > > > Sent: Thursday, April 05, 2007 19:32 > > > > > To: kde@freebsd.org > > > > > Cc: x11@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 no= w. > > > > > > 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@. > > > > > > > > > > > > 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 X11BA= SE > > > > 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. > > > > Since I understand there will be an update script for the upcoming X.org > > upheaval, this issue would be a prime candidate for handling it in such= a > > script. flz, lesi, what do you think? > > Would bumping revision of qmake and qt be enough or were you thinking of > something more aggressive? No - I'm guessing the problem is that qmake generates wrong dependencies in= =20 Makefiles when it configures Qt with a prefix that is different from the on= e=20 of a previously installed Qt, with the dependencies being generated on file= s=20 in the destination install prefix instead of the workdir. The most obvious= =20 workaround: Deinstall (as in make deinstall) qt33, then (and only then)=20 rebuild and reinstall qt33 with the new PREFIX set. An update script could= =20 take care of this rather easily as part of a post-update cleanup routine. I can also try to reproduce this and, if I succeed, try to come up with som= e=20 post-configure in-place Makefile editing, if my guess turns out to be=20 correct, but I am still busy with changing a number of qt4 ports to avoid=20 conflicting with qt33 after the X11BASE-move and flz@ already told me would= =20 very much like to remain on schedule and do the merge on the upcoming=20 monday - I'm simply not sure I will be able to address this problem in time. Another option would be doing nothing, writing up an UPDATING entry and=20 pointing disgruntled users to that, of course. ;) Cheers, =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart51220347.OT21hAQaud Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGJRjlXhc68WspdLARAndQAJ9S27rpdDUGSZSjMsMc/THM0A0JyQCfZ9dx iUTHKCSfBTQKXFQGkr2fl5w= =EtsW -----END PGP SIGNATURE----- --nextPart51220347.OT21hAQaud--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704172058.53674.lofi>