Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Feb 2025 15:51:53 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 245495] www/qt5-webengine: build failure after devel/re2 upgrade
Message-ID:  <bug-245495-7788-hV2UN6u30y@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-245495-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-245495-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245495

--- Comment #10 from John Hein <jcfyecrayz@liamekaens.com> ---
(In reply to Robert Clausecker from comment #9)
CONFLICTS_BUILD with the installed port itself will not trigger because of =
this
in the conflict check (in the default conflicts check implementation in
bsd.port.mk):

"%n !=3D ${PKGBASE}"

That expression is part of the 'pkg query' and prevents the port from
conflicting with itself (unless a port changes its naming scheme such that
PKGBASE is different than what it was when the port was originally installed
which is unusual - and doesn't help with the problem you are trying to solv=
e:
early notification of a situation that is known to commonly cause failures =
at
some point in the [long, in this port's case] build).

You could override the default check-build-conflicts, however.  Or convince
someone to remove that self-check exception.

The kde/qt porting team has looked into ways to isolate a build in a working
area (WRKDIR) from what is installed (in LOCALBASE).  Given the complexitie=
s of
the qt build system, that is a hard problem.  They have tried.  I can't spe=
ak
for everyone on that team, but I believe that until someone comes up with an
acceptable solution (submit patches for testing), I don't think they have t=
he
time or motivation to spend more time trying to find a way.  I may be wrong=
.=20
But unless someone on this bug (or any other open bugs related to this issu=
e)
has the inclination to dig in and try to solve it themselves, I think it is
appropriate to give up and mark the bug with WONTFIX (with a good explanati=
on).

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245495-7788-hV2UN6u30y>