Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Feb 2022 22:47:53 +0100
From:      Stefan Esser <se@FreeBSD.org>
Cc:        ports@FreeBSD.org
Subject:   Re: graphics/jasper failed again !!!
Message-ID:  <8bbfb05b-92d7-cd4a-8de0-7ba556161158@FreeBSD.org>
In-Reply-To: <PSAPR03MB56394B88E7FFA74542765101FA019@PSAPR03MB5639.apcprd03.prod.outlook.com>
References:  <202202281047.21SAlrMx049534@kx.truefc.org> <PSAPR03MB56394B88E7FFA74542765101FA019@PSAPR03MB5639.apcprd03.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.02.22 um 22:08 schrieb Tatsuki Makino:
> Hello.
> 
> The problem is described here.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260878
> It appears to have been closed, to be upgraded to 3.0.x.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262039
> 
> A workaround for this problem is to temporarily remove pkgconfig.

Thank you for the information about the existing PR.

This is not the only port that needs to ignore information
provided by pkg-config. I have recently fixed another one
by forcing it to ignore the data provided by pkg-config.

This is a systematic pkg-config issue, and that was the
reason to include a CC to bapt@ (who was active in this
area).

It should never be the case that respecting pkg-config
information results in worse configure results than the
probes executed when pkg-config is not available.

Looking at the CMAKE output and variables generated
without pkg-config it seems that the glut.pc file does
not correctly list all include and library dependencies.

But I do not know enough about cmake and pkg-config to
know how to fix these build issues.

Upgrading the jasper port may solve it for this port, but
the issue that pkg-config can brake port builds persists
and should be resolved.

Regards, STefan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8bbfb05b-92d7-cd4a-8de0-7ba556161158>