[Pkg-electronics-devel] Bug#1103550: closed by Andreas Bombe <aeb at debian.org> (Re: Bug#1103550: Broken libghdl-5-0-1)

[Andreas Bombe]

Am Sun, Jul 20, 2025 at 11:44:34PM +0200, schrieb Paebbels:
> One question: Did you write the test execution framework in GitHub
> Actions or did I write it?

I have touched nothing in regards to GitHub. The mentioned autopkgtest
is a Debian CI framework and I configured that to run the GHDL test
suite against installed ghdl packages. There's also a GitLab instance
used in Debian which also offers CI functionality but that is separate.

> --libghdl-name, --libghdl-library-path and --libghdl-include-dir are
> CLI arguments to the GHDL executable, they don't reflect setting in
> libghdl if not patched correctly.

They are of course patched to return the correct paths in the Debian
package. Or rather, the Get_Libghdl_Path function in Ghdllib is patched.

> Executing a testcase like issue2005 doesn't run more elaborate tests
> like using GHDL's language server. If you execute more tests, you'll
> see the VHDL sources are not found by libghdl. If these files are not
> found by libghdl, it's an almost useless installation.

True, the issue2005 test only checks for successful linking (and is the
only test in the test suite that directly accesses libghdl). However,
the libghdl package was working for the yosys ghdl plugin. Once I
include the Python packaging, I will of course take care of it working
correctly.

If the unmodified pyGHDL should work, then it needs its library
searching expanded to either query the path from ghdl or consider
multiarch subdirectories under /usr/lib.

> Please share your patches at https://github.com/ghdl/ghdl/issues and
> we can review your findings.

It's true that I neglected reporting a bunch of these issues upstream
this time around. I think I will do that after packaging the next
version after the Debian release.