Moin moin Intersting. I would assume that synth is smart enough to bulild qmake/buildtools first before upgrading anything else Qt-releated. So I suspect youou might have some stale files in /usr/local which are not part of any package (any more). When you have found the file that Alsono pointed you to, could you check with `pkg which' from whence it comes?
mfg Tobias On Fri, 26 Oct 2018 at 22:37, Andrew Hamilton-Wright < andrew.hamilton-wri...@uoguelph.ca> wrote: > > > As it happens, I do use synth for port management. That does not solve > the problem. In fact, it was problems in synth build that let me to look > into this issue in the first place. > > > > What is clear to me is that the port installation of qt5 as it exists on > my machine is broken, as it cannot be built from the port itself, which is, > I note the recommended way of doing things as described in the FreeBSD > manual. > > > > The machine is up to date. When building, I see the 5.11.2 version number > for QT being reported at multiple points, however the build itself is > getting the old version information from somewhere. > > > > Where are these “hidden” data pieces stored? It would be helpful to know > where the clearly incorrect version numbering is coming from. > > > > If, to do this, I do need to completely remove QT, a pointer to some > instructions on how to do that would be helpful. It does not seem to > simply be the case that either port based “make deinstall” or package based > delete has any effect on the problem. Wherever the corruption is, it is > not touched by these methods. > > > > Is there a clear statement somewhere about where this information is > stored? Or additionally how to ensure that the entirety of QT is removed > in order that it can be reinstalled from scratch? > > > > Best regards, > > AHW > > > > > > *From: *"Tobias C. Berner" <tcber...@gmail.com> > *Date: *Friday, October 26, 2018 at 2:54 PM > *To: *Schaich Alonso <alonsoscha...@fastmail.fm> > *Cc: *Andrew Hamilton-Wright <andrew.hamilton-wri...@uoguelph.ca>, > "k...@freebsd.org" <k...@freebsd.org> > *Subject: *Re: qt5-core not building > > > > Moin moin > > > > > > Your wasting time by not building with poudriere or synth :). > > Qt5 is meant to be used as a blob. There is very limited support for > version matching. > > > > All in all the Qt ports have become more robust and in that normally they > do not use the files installed for building (as we have "hidden" them in a > prefix). So upgrades tend to work if you don't just go for the last in the > chain blindly. > > Hovewer... You need to make sure qmake and such are up to date... And > then, work on the rest of the qt5 base.... > > To answer your question, the include path mess was demessed :) > > > > > > For major qt version upgrades you need to rebuild the consumers anyways. > > > > > > Mfg Tobias > > > > Schaich Alonso <alonsoscha...@fastmail.fm> schrieb am Fr., 26. Okt. 2018, > 19:21: > > On Fri, 26 Oct 2018 12:02:51 +0200 > "Tobias C. Berner" <tcber...@gmail.com> wrote: > > > Moin moin > > > > Your Qt5 seems way out of date. As the version string is 5.9.4. > > Please update your ports tree and packages to be up to date. > > > > > > Mfg Tobias > > Hi > > There is also indication that both Qt-5.9.4 and 5.11.2 are being used > at the same time. > > There used to be issues when updating Qt using ports rather than pkgng, > the workaround back then (last year) was to uninstall the old Qt and > installing the new one so the build process wouldn't mix the versions > when building the "new" Qt. > > I'm still removing my old Qt installations before building the new ones > these days, which is a pain since removing Qt also removes KDE and > other Qt consumers. > > Am I wasting time rebuilding half the system rebuilding half my system > on updates that don't even break ABI, or do we still suffer from qmake > messing up the include paths? > > Alonso > >