Date: Sun, 25 Apr 2021 20:11:56 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 254751] devel/e2fsprogs-libss: fails to build with /bin/sh: compile_et: not found Message-ID: <bug-254751-7788-aJpKEvHREe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254751-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-254751-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254751 --- Comment #4 from Benjamin Kaduk <bjk@FreeBSD.org> --- (In reply to Felix Palmen from comment #3) > I had no idea compile_et is related to kerberos. Indeed, I build my base = without kerberos and use MIT krb5 from ports. Will have a look whether comp= ile_et is provided there=E2=80=A6 MIT krb5 does have a compile_et script in its build (bourne shell and awk),= and it's in the pkg-plist for the FreeBSD port, so I think it should be suitable for this purpose. > Would this also solve the other problem I came across (circular dependenc= y around libcom_err)? Or did I misunderstand something there? I think so -- despite the name being for a "common error-reporting library", there are quite a number of libcom_err implementations around, including fr= om the major kerberos implementations. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254751-7788-aJpKEvHREe>