https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
Max Brazhnikov changed:
What|Removed |Added
CC||m...@freebsd.org
--- Comment #3 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
--- Comment #2 from Baptiste Daroussin ---
ok if ccmake people are ok with it.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
--- Comment #7 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=56538adacf53391307f687155be3fc787a95f40b
commit 56538adacf53391307f687155be3fc787a95f40b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
Yuri Victorovich changed:
What|Removed |Added
Assignee|port...@freebsd.org |y...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
--- Comment #5 from Yuri Victorovich ---
(In reply to Max Brazhnikov from comment #3)
> Is there other need to set CMAKE_C_COMPILER_LAUNCHER? If yes, we should allow
> user to override it.
This appears to be outside of the scope of the i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
--- Comment #4 from Yuri Victorovich ---
(In reply to Max Brazhnikov from comment #3)
> If the problem is not specific to USES=llvm, shall we enable compiler
> launcher unconditionally when ccache is used?
ccache only supports C/C++ comp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284893
Yuri Victorovich changed:
What|Removed |Added
Summary|Fix ccache when ports has |Fix ccache for ports that
