Seth Turner wrote:
I am just starting out with BLFS, but have built LFS many times over the
years (for learning). I see that MIT Kerberos is an optional dependency
for OpenSSL. My build plan is as follows:
which-2.21
valgrind-3.11.0
tcl-8.6.6
expect-5.45
dejagnu-1.6
libffi-3.2.1
keyutils-1.5.9
openssl-1.0.2h
python-2.7.12 (openssl is opt dep)
cracklib-2.9.6
linux-pam-1.3.0
shadow-4.2.1
libcap-2.25
libevent-2.0.22
ntp-4.2.8p8
mit kerberos v5-1.14.3 (python-2.7.12 is opt dep)
I have found instructions on the MIT Kerberos website to build with
support for OpenSSL. My question is: After building MIT Kerberos and
installing it, should I go back and re-build OpenSSL to take advantage of
OpenSSL's optional dependency on MIT Kerberos? And possibly the other
things that needed OpenSSL (like Python)?
Also, how would I be able to determine the answer to this type of question
on my own? I figure there will be more times where package-foo has
optional dependency on package-bar and at the same time package-bar has
optional dependency on package-foo.
What you have discovered is that there are circular dependencies in the
packages. If you need a particular feature, then go back and rebuild the
dependent package similar to the freetype/harfbuzz process documented in
the book.
What I have found is that the extra functionality is rarely needed.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
