Date: Sat, 28 Jan 2023 15:51:01 +0100 From: Matthias Andree <matthias.andree@gmx.de> To: Dima Panov <fluffy@FreeBSD.org> Cc: =?UTF-8?Q?Jean-S=c3=a9bastien_P=c3=a9dron?= <dumbbell@FreeBSD.org>, ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: 75ac7903573c - main - graphics/darktable: Use GCC as the compiler instead of LLVM Message-ID: <3e6b66b1-c01e-095a-fb95-61db65787d9b@gmx.de> In-Reply-To: <e7503770-7637-2880-e374-ba4f3b8ee402@FreeBSD.org> References: <202301272245.30RMjpHY013683@gitrepo.freebsd.org> <e7503770-7637-2880-e374-ba4f3b8ee402@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
Am 28.01.23 um 14:22 schrieb Dima Panov: > Moin-moin! > > > USES+= llvm:14,build > > with > > USES+= compiler:gcc-c++11-lib > USE_GCC=yes > > at same time? > Please choose only one set, compiler.mk have a higher priority and > conflicting with overriding CC > > BTW, USES=llvm also needs to set USE_CXXSTD='gnu++17', for example > Dima, thanks for looking again. I can't judge on the details because that's been Jean-Sébastien's doing, but I know that darktable uses two compilers: - one is for the C++ librawspeed and the C darktable code, and - the other compiler shall be LLVM to compile the OpenCL kernels. I don't think GCC could do the latter, and certainly darktable expects to use LLVM by way of its build tooling and configuration (cmake-based). Jean-Sébastien switched the C/C++ compiler from LLVM to GCC. If that raises conflicts, I wonder what those would be, and what to watch out for in the logs or at run-time, and that a "make reinstall" or "poudriere bulk -tC" would not catch. Both Jean-Sébastien and I, independently, have successful builds with both GCC and LLVM. I have not yet tested OpenCL at run-time though. So...? Cheers, Matthiashome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3e6b66b1-c01e-095a-fb95-61db65787d9b>