On 2017-07-30 12:17 -0700, Daniel Schepler wrote:
> Source: libdrm
> Version: 2.4.82-1
> Severity: wishlist
>
> Currently, libdrm is involved in build dependency cycles such as:
>
> libdrm Build-Depends on valgrind
> valgrind Build-Depends on gdb
> gdb Build-Depends on texlive-base
> texlive-base Depends on texlive-binaries
> texlive-bin Build-Depends on libgd-dev
> libgd2 Build-Depends on libtiff-dev
> tiff Build-Depends on freeglut3-dev
> freeglut Build-Depends on libgl1-mesa-dev
> mesa Build-Depends on libdrm-dev
>
> As far as I can tell, it should be sufficient just to annotate the
> Build-Depends with "valgrind <!nocheck>".
Really? There seems to be quite a bit of code that's conditional to
#ifdev HAVE_VALGRIND, e.g. in intel/intel_bufmgr_gem.c, and I don't
think building with the nocheck profile should alter the produced binary
packages.
Cheers,
Sven
