Your message dated Thu, 04 May 2023 20:52:14 -0600
with message-id <[email protected]>
and subject line Re: Bug#1035489: krb5-config: missing dependency to C compiler
has caused the Debian Bug report #1035489,
regarding krb5-config: missing dependency to C compiler
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.)
--
1035489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035489
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libkrb5-dev
Version: 1.20.1-1+b1
Severity: important
Dear Maintainer,
the krb5-config tool needs a C compiler to work at all:
krb5-config
/usr/bin/krb5-config: 1: cc: not found
Failed to find installation architecture
To reproduce, just install libkrb5-dev (e.g. in the debian:bookworm
container) and call krb5-config. Once a cc is installed (e.g. gcc), the
tool works properly.
This bug affects at least bullseye and bookworm.
Best regards,
Felix Moessbauer
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libkrb5-dev depends on:
ii krb5-multidev 1.20.1-1+b1
libkrb5-dev recommends no packages.
Versions of packages libkrb5-dev suggests:
pn krb5-doc <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
I'd definitely say that krb5-config should be used only in the context
of building software. Yes, it does have --vendor and --version, but I'd
recommend those only be used as part of doing a build, not say, as a
good way of detecting which Kerberos is installed for system
administration.
(klist -V and/or klist --version or kinit --version are better guesses
for figuring out what is installed).
So I'm closing.
--Sam
--- End Message ---
