Your message dated Sun, 20 Jul 2025 16:17:18 +0200
with message-id 
<2y34raupvqrw6kbvo4jokyepxs3byh5vekdpbzmxzaw72po53u@227iwzrssswp>
and subject line Re: Bug#1103544: Executable installed into /usr/lib
has caused the Debian Bug report #1103544,
regarding Executable installed into /usr/lib
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1103544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103544
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ghdl-llvm
Version: 5.0.1+dfsg-1+b1

Hi,

when installing GHDL with LLVM backend, an executable (here
ghdl1-llvm) gets installed into /usr/lib/ghdl/llvm. Correct me if I'm
wrong, but I have never seen any executables in /usr/lib/...

The analogy of ghdl1-llvm is similar to cc1 in gcc. cc1 is installed into
/usr/libexec/gcc/x86_64-linux-gnu/13/cc1

/usr/libexec/.... sounds better than /usr/lib/....

Further notes on the LLVM backend:
The new llvm-jit backend is not yet included as a new package.

Kind regards
    Patrick

--- End Message ---
--- Begin Message ---
Am Fri, Apr 18, 2025 at 11:02:07PM +0200, schrieb Paebbels:
> when installing GHDL with LLVM backend, an executable (here
> ghdl1-llvm) gets installed into /usr/lib/ghdl/llvm. Correct me if I'm
> wrong, but I have never seen any executables in /usr/lib/...
> 
> The analogy of ghdl1-llvm is similar to cc1 in gcc. cc1 is installed into
> /usr/libexec/gcc/x86_64-linux-gnu/13/cc1
> 
> /usr/libexec/.... sounds better than /usr/lib/....

/usr/libexec is optional per the Filesystem Hierarchy Standard and used
in Debian mostly for historical reasons. The standard location for
executables that are not supposed to be in $PATH is somewhere under
/usr/lib.

Closing this as it does not describe an actual bug.

> Further notes on the LLVM backend:
> The new llvm-jit backend is not yet included as a new package.

This is a separate issue and I may have either missed this or decided
against it. I'll consider it when updating the packaging after the
soon to happen Debian release.

--- End Message ---

Reply via email to