Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Sep 2023 11:29:41 -0400 (EDT)
From:      Gerald Pfeifer <gerald@pfeifer.com>
To:        Yuri Victorovich <yuri@FreeBSD.org>
Cc:        ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org,  dev-commits-ports-main@FreeBSD.org
Subject:   =?UTF-8?Q?Re=3A_git=3A_dff2adf1dc0d_-_main_-_cad=2Fopentimer?= =?UTF-8?Q?=3A_Update_g20210726_=E2=86=92_g20221116?=
Message-ID:  <65bd525a-9067-8161-2a4b-9d546b5cf0d1@pfeifer.com>
In-Reply-To: <202307230850.36N8oide010742@gitrepo.freebsd.org>
References:  <202307230850.36N8oide010742@gitrepo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Yuri,

On Sun, 23 Jul 2023, Yuri Victorovich wrote:
> URL: https://cgit.FreeBSD.org/ports/commit/?id=dff2adf1dc0df08a79ae5da077cb852f584b190e

> -USE_GCC=	yes # fails to build with clang-11: https://github.com/OpenTimer/OpenTimer/issues/48
> +#USE_GCC=	yes # fails to build with clang-11: https://github.com/OpenTimer/OpenTimer/issues/48

Does this mean it now builds with current clang? The commit message did 
not mention anything.

Any objection to me removing this old trace of USE_GCC in that case?
(I'm keeping an eye on those, in case you wonder.)

Gerald



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?65bd525a-9067-8161-2a4b-9d546b5cf0d1>