On 1/16/20 4:14 PM, Alan Feuerbacher via blfs-support wrote:
On 1/16/2020 12:51 AM, Pierre Labastie via blfs-support wrote:
Le 16/01/2020 à 02:37, Alan Feuerbacher via blfs-support a écrit :
In building mesa-19.3.2 I found that configure requires two programs
that are
listed in the BLFS book as recommended, or not at all:
Wayland-1.17.0
Wayland-protocols-1.18
Since they are recommended, they are assumed to be present when
running our
instructions. They are not strictly required, but you may need some added
"--disable" switch if they are not present. See the link passed by
Douglas,
paragraph "Dependencies".
I also found that "ninja install" must be done before "ninja test".
Otherwise
libglapi.so is not found and the tests fail.
The same is true for pixman-0.38.4 . Install must come before test.
The same is true for libepoxy-1.5.4 . Install must come before test.
I think you have the same permission problem as for git: try building and
running the tests as a normal user. I bet the libraries would be found
then.
Pierre
You're right about the permissions problem: I've been building and
testing as root during this entire build. I changed the owner of all
appropriate files in my LFS system from root:root to lfs:wheel, since
lfs is unprivileged, and then built the offending packages again. All ok
now.
This brings up something I'm a bit confused about: Several years ago one
of you LFS staff guys suggested that I build everything as root, since
that was his own practice, even though not recommended by LFS staff. But
it's now clear to me that the staff recommendations really ought to be
followed, which I'm doing from now on.
So in building more packages, I'm going to be switching back and forth
between users root and lfs. After awhile my brain objects to this, and
in the past I've gotten a bit confused as to who I am -- hence the staff
guy's suggestion to stay root.
I've been trying to think of a way to more or less automate this
switching, but there are complications I can't figure out. You who use
jhalfs seem to have this figured out. What do you suggest that I do?
Especially since building BLFS is supposed to not be automated.
When the book says "as the root user", just use sudo.
sudo command options ...
Personally I use some extra options when building sudo:
--enable-shell-sets-home \
--enable-noargs-shell \
--disable-root-sudo \
--with-logfac=auth \
--without-pam \
--without-sendmail
Also, it's important to know who you are at any time. Use something
like this in ~/.bashrc and /root/.bashrc:
HOST=`cat /etc/hostname`
NORMAL="\[\e[0m\]"
RED="\[\e[1;31m\]"
GREEN="\[\e[1;32m\]"
CYAN="\[\e[1;36m\]"
if [[ $EUID == 0 ]] ; then
PS1="$RED\u$NORMAL@$HOST$RED [ $NORMAL\w$RED ]# $NORMAL"
else
PS1="\u$GREEN@$CYAN$HOST$GREEN [ $NORMAL\w$GREEN ]\$ $NORMAL"
fi
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
