From owner-freebsd-x11@FreeBSD.ORG Tue Apr 17 23:41:12 2007 Return-Path: X-Original-To: freebsd-x11@freebsd.org Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0748916A407 for ; Tue, 17 Apr 2007 23:41:12 +0000 (UTC) (envelope-from lofi@freebsd.org) Received: from mail-in-07.arcor-online.net (mail-in-07.arcor-online.net [151.189.21.47]) by mx1.freebsd.org (Postfix) with ESMTP id 79D0D13C4B0 for ; Tue, 17 Apr 2007 23:41:11 +0000 (UTC) (envelope-from lofi@freebsd.org) Received: from mail-in-01-z2.arcor-online.net (mail-in-01-z2.arcor-online.net [151.189.8.13]) by mail-in-07.arcor-online.net (Postfix) with ESMTP id 66985252D9D; Tue, 17 Apr 2007 20:59:05 +0200 (CEST) Received: from mail-in-05.arcor-online.net (mail-in-05.arcor-online.net [151.189.21.45]) by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id A372512DD71; Tue, 17 Apr 2007 20:59:04 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-184-171.pools.arcor-ip.net [84.61.184.171]) by mail-in-05.arcor-online.net (Postfix) with ESMTP id 9BD6223B0D6; Tue, 17 Apr 2007 20:59:03 +0200 (CEST) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.2]) by lofi.dyndns.org (8.13.8/8.13.3) with ESMTP id l3HIwuv8032952 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 17 Apr 2007 20:58:56 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.6/8.13.4) with ESMTP id l3HIwuWV055438; Tue, 17 Apr 2007 20:58:56 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.6/8.13.4/Submit) id l3HIwstQ055421; Tue, 17 Apr 2007 20:58:54 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: Dejan Lesjak Date: Tue, 17 Apr 2007 20:58:42 +0200 User-Agent: KMail/1.9.6 References: <200704051229.27994.lists@jnielsen.net> <200704171633.59007.lofi@freebsd.org> <200704171638.39985.dejan.lesjak@ijs.si> In-Reply-To: <200704171638.39985.dejan.lesjak@ijs.si> X-Face: g:jG2\O{-yqD1x?DG2lU1)(v%xffR"p8Nz(w/*)YEUO\Hn%mGi&-!+rq$&r64,=?utf-8?q?fuP=7E=3Bbw=5C=0A=09=5EQdX?=@v~HEAi?NaE8SU]}.oeYSjN84Fe{M(ahZ.(i+lxyP; pr)2[%mGbkY'RmM>=?utf-8?q?+mg3Y=24ip=0A=091?=@Z>[EUaE7tjJ=1DRs~:!uSd""d~:/Er3rpQA%ze|bp>S MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart51220347.OT21hAQaud"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200704172058.53674.lofi@freebsd.org> X-Virus-Scanned: by amavisd-new Cc: freebsd-x11@freebsd.org, Andy Fawcett , kde@freebsd.org Subject: Re: [kde-freebsd] qt upgrade strangeness X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2007 23:41:12 -0000 --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--