[libcamera-devel] lc-compliance build regression for virtualized environment

[Laurent Pinchart]

Hi Nícolas,

All my apologies for having missed your e-mail and replying so late :-S

On Wed, Feb 02, 2022 at 11:30:03AM +0000, Kieran Bingham wrote:
> Quoting Nícolas F. R. A. Prado (2022-01-11 20:47:11)
> > Hello,
> > 
> > Commit 0d50a04cc918 ("lc-compliance: Build with gtest in subprojects") broke the
> > compilation of lc-compliance for KernelCI. The issue seems to come from some
> > interaction of meson's wrapdb mechanism with the virtualization used in KernelCI
> > (docker container).
> 
> Intersting. That commit states:
> 
> >> libgtest-dev is provided as a static library at least by Debian 10.
> >> The compiler and linker to create the static library might be
> >> different from ones used for libcamera. This causes a problem upon
> >> linking.
> 
> And I recall that before that patch, I had build issues on my system
> which I use to build both clang and gcc builds. So I believed this
> patch was beneficial at the time.
> 
> I've now also just heard from Javier that this is breaking the RedHat
> packaging system, so we'll need to find a more generalised solution
> somehow I think.

Javier has submitted a patch ([1]) which I've successfully tested. Could
you give it a try ?

[1] https://lists.libcamera.org/pipermail/libcamera-devel/2022-February/028920.html

> > For the time being, that commit is reverted when compiling lc-compliance in
> > KernelCI.
> > 
> > This does look like a bug in either meson or docker. So this email is mostly to
> > let you know about this issue. Unless this is already some known issue, or a fix
> > for it is already know, in which case I'd love to hear about it.
> > 
> > Link for the issue: https://github.com/kernelci/kernelci-core/issues/887

-- 
Regards,

Laurent Pinchart