[SOLVED] Question about libva install in mesa 8.4 systemd build
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Question about libva install in mesa 8.4 systemd build
Hi Friends,
I think I been doing something wrong when it comes to installing Mesa and libva. I'm lost about this:
libva-2.4.0 (to build drivers for supported hardware, note that there is a circular dependency. You must build libva first without EGL and GLX support, install this package, and rebuild libva.) What is EGL AND GLX and what should I do? I have been having trouble later on when get to printers install because freeglut fails because it says glu missing.
Thanks for your time and help,
Danny
Distribution: LFS 9.0 Custom, Merged Usr, Linux 4.19.x
Posts: 616
Rep:
There are several circular dependencies in the low level / legacy graphics stack. This is how I build them,
packages prefixed with a + indicate a rebuild / reinstall...
That gets you the basic setup with an xterm, clock and window manager. You're setup to go from this point to build any or all of the avaiable toolkit stacks for desktops: EFL, GTK+, Qt. My startx opens a single xterm and xclock for running make checks on subseqent packages like GTK+ 2.25, etc. My xinitrc...
Code:
#!/bin/sh
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/app-defaults/.Xresources
sysmodmap=/etc/X11/app-defaults/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi
if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
# start some nice programs
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec openbox &
xclock -d -brief -twelve -geometry 90x35+0+0 &
exec xterm -geometry 80x40+120+0 -name login
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.