On 08/24/2014 08:00 AM, ALZ (phyglos.org) wrote:
On 08/24/2014 02:47 AM, Ken Moffat wrote:
On Sat, Aug 23, 2014 at 11:19:07PM +0200, ALZ (phyglos.org) wrote:
Hi,
I'm building Xorg from BLFS last-SVN, been the first package in this
group
to be compiled libdrm-2.4.56.
It just stops at ./configure with...
=================================================================================
Building: libdrm-2.4.56 |tar.bz2| () at Sat Aug 23 22:31:09 CEST 2014
=================================================================================
[...]
configure: error: Package requirements (pciaccess >= 0.10) were not met:
No package 'pciaccess' found
---
Detailed log shows...
[...]
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for CAIRO... yes
checking whether to enable Cairo tests... yes
checking for LIBUDEV... yes
checking for xsltproc... no
checking for docbook manpages stylesheet... no
checking for native atomic primitives... Intel
checking for PCIACCESS... no
and the build ends.
I'm compiling in VMware Workstation 10 and previous libdrm from last
mid-June worked well (I'm using that host to write this email).
Is this "pciaccess" library now required in order to build in VMware?
I know nothing about VMware, but libpciaccess is part of the Xorg
libraries.
http://www.linuxfromscratch.org/blfs/view/svn/x/x7lib.html
So it seems incorrect to move libdrm before the Xorg Libraries set, in
spite of the later been "just recommended for a particular case".
>>
libdrm Dependencies
Recommended
Xorg Libraries (for Intel KMS API support required by Mesa)
<<<
from http://www.linuxfromscratch.org/blfs/view/svn/x/libdrm.html
I'm moving libdrm after Xorg libraries and will confirm back.
Building libdrm after libpciacces did not solve the problem (!!??).
I don't like this behaviour; it maybe points to another underlying cause.
From ./configure --help, I've got:
--disable-libkms Disable KMS mm abstraction library (default:
auto)
--disable-intel Enable support for intel's KMS API (default:
auto)
--disable-radeon Enable support for radeon's KMS API (default:
auto)
--disable-nouveau Enable support for nouveau's KMS API
(default: auto)
--disable-vmwgfx Enable support for vmwgfx's KMS API (default:
yes)
Besides inconsistent descriptions (does --disable do enable? so what's
the default value?), I tried an explicit configuration for vmware:
./configure --prefix=/usr \
--disable-intel \
--disable-radeon \
--disable-nouveau \
--enable-vmwgfx \
--enable-udev &&
make
I'm now able to build libdrm (after Xorg libs, where it will stay), at
the cost of two failed tests.
=================================================================================
Building: libdrm-2.4.56 |tar.bz2| () at Sun Aug 24 08:28:45 CEST 2014
=================================================================================
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4 ${ACLOCAL_FLAGS}
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: Leaving directory `.'
../build-aux/test-driver: line 107: 19154 Aborted "$@" >
$log_file 2>&1
../build-aux/test-driver: line 107: 19178 Aborted "$@" >
$log_file 2>&1
make[4]: *** [test-suite.log] Error 1
make[3]: *** [check-TESTS] Error 2
make[2]: *** [check-am] Error 2
make[1]: *** [check-recursive] Error 1
make: *** [check-recursive] Error 1
libtool: install: warning: relinking `libkms.la'
real 0m35.561s
user 0m19.091s
sys 0m17.115s
I don't like this solution at all.
This needs more homework before posting back again.
ALZ.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
