On 1/3/20 3:48 AM, Pierre Labastie via lfs-dev wrote:
Le 02/01/2020 à 23:53, Bruce Dubbs via lfs-dev a écrit :
On 1/2/20 3:26 PM, Pierre Labastie via lfs-dev wrote:
Hi,
First, the variable for naming the static library has changed, and now there
are two of them: They can be removed with:
sed -i '/install.*STA...LIBNAME/d' libcap/Makefile
I thought I did that. Evidently forgot to get it in the book's source.
Second, we use prefix=/usr for Make install, then move the shared library to
/lib. But actually, if we do not pass prefix, the shared library is directly
installed in /lib (note, we do need to pass lib=lib, but now RAISE_SETFCAP=no
is the default). The only difference is that some binaries are installed in
/usr/sbin if we pass prefix=/usr and they are installed in /sbin if not. Not a
big deal, we do not use them anyway...
I'll make a test build with the sed above and just "make lib=lib install"
(without touching the library), and change the book if everything is OK.
OK, thanks.
Hmm, did a build of SysV, while the real user of libcap is systemd.
Restarting...
However, I've found that coreutils can use libcap for ls --color (colors
depending on capabilities...)
I do not know whether I should change the dependency file: clearly, the
dependency of coreutils on libcap is optional, but we get more functionality
if libcap is installed. What should I do?
Pierre
In this case, I think we should put it in "Installation depends on:". In
the BLFS bash startup scripts, we create 'dircolors', which if I'm not
mistaken, is used to give "ls --colors" a color map.
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
