Zhihao Yuan wrote at 17:45 -0600 on Mar 1, 2011:
> I know what you mean, exactly. That's exactly what I want to do, build
> libdrm 2.4.17 with --disable-radeon-experimental-api and
> WITHOUT_NOUVEAU=1 for other ports. Yes. But I don't know why, after I
> done this for libdrm, libGL, liBGLU, I found that I can not build dri
> 7.6.1 since HAVE_LIBDRM_RADEON is 1 in such case. As you said, it
> should not be, but it does happen.
It is set that way probably because dri's configure script really
did _set_ HAVE_LIBDRM_RADEON=yes.
And it probably set HAVE_LIBDRM_RADEON=yes because there is something
non-standard on your system.
Let's look at part of the dri configure script...
if test -n "$PKG_CONFIG" && \
{ { $as_echo "$as_me:${as_lineno-$LINENO}: \$PKG_CONFIG --exists --print-errors \"libdrm_radeon libdrm >= \$LIBDRM_RADEON_REQUIRED\""; } >&5
($PKG_CONFIG --exists --print-errors "libdrm_radeon libdrm >= $LIBDRM_RADEON_REQUIRED") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then
pkg_cv_LIBDRM_RADEON_LIBS=`$PKG_CONFIG --libs "libdrm_radeon libdrm >= $LIBDRM_RADEON_REQUIRED" 2>/dev/null`
So what does 'pkg-config --exists --print-errors "libdrm_radeon libdrm"'
show on your system?
The configure script should only set HAVE_LIBDRM_RADEON=yes if the
above succeeds.
If it does succeed, then somehow you got libdrm_radeon (i.e.,
libdrm_radeon.pc) installed. But that should not be installed
if libdrm is built with --disable-radeon-experimental-api (as
it is currently set to be built in graphics/libdrm 2.4.17).
config.log might also tell more.