Re: make coverage-html would fail within build directory separate from source tree

On 2021-Mar-04, walker wrote:

> Hi, hackers
>
> During installation from source code, I created a build directory separate from the source tree, and execute the following command in the build directory:
> /home/postgres/postgresql-13.2/configure -- enable-coverage
> make
> make check
> make coverage-html
>
>
> However, while executing make coverage-html, it failed with the following error messages:
> /bin/lcov --gcov-tool /bin/gcov -q --no-external -c -i -d . -d /home/postgres/postgresql-13.2/ -o lcve_base.info
> ...
> geninfo: ERROR: no .gcno files found in /home/postgres/postgresql-13.2/!
> make: *** [lcov_base.info] Error 255
> make: *** Deleting file 'lcov_base.info'

Hmm, it works fine for me. config.log says I do this (in
/pgsql/build/master-coverage):

$ /pgsql/source/REL_13_STABLE/configure --enable-debug --enable-depend --enable-cassert --enable-coverage --cache-file=/home/alvherre/run/pgconfig.master-coverage.cache --enable-thread-safety --enable-tap-tests --with-python --with-perl --with-tcl --with-openssl --with-libxml --with-tclconfig=/usr/lib/tcl8.6 PYTHON=/usr/bin/python3 --prefix=/pgsql/install/master-coverage --with-pgport=55451

I do run "make install" too, though (and "make -C contrib install").
Not sure if that makes a difference.
But for sure there are no .gcno files in the source dir -- they're all
in the build dir.

--
Álvaro Herrera Valdivia, Chile
"La persona que no quería pecar / estaba obligada a sentarse
en duras y empinadas sillas / desprovistas, por cierto
de blandos atenuantes" (Patricio Vogel)