On Monday 28 February 2005 05:05 pm, [EMAIL PROTECTED] wrote:
> You might want to investigate why those particular x-include and x-library
> values are needed at all - is your system *not* checking /usr/include and
> /usr/lib by default already?
no, after glancing at the new configure.in, i'm pretty sure the bug here is
this bit of logic:
<snip>
if test "x$have_x" = "xyes"; then
if test "x$x_includes" != "x"; then
x_cflags="-I$x_includes"
fi
if test "x$x_libraries" != "x"; then
x_libs="-L$x_libraries -lX11 -lXext"
fi
AM_CONDITIONAL(BUILD_X11, true)
AC_DEFINE(BUILD_X11, 1, [enabling X11 support])
else
</snip>
x_libs is only set to '-lX11 -lXext' if x_library is a valid path ? talk
about bogus ... here's some sane logic:
<snip>
x_libs="-lX11 -lXext"
if test "x$x_libraries" != "x"; then
x_libs="-L$x_libraries $x_libs"
fi
</snip>
-mike
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
