I digged a little around libxcb-1.4, which is the first X related
package which fails.
In the configure script, line 12791, the script looks for the
xcbincludedir :
# Find the xcb-proto protocol descriptions
{ $as_echo "$as_me:$LINENO: checking XCBPROTO_XCBINCLUDEDIR" >&5
$as_echo_n "checking XCBPROTO_XCBINCLUDEDIR... " >&6; }
XCBPROTO_XCBINCLUDEDIR=`$PKG_CONFIG --variable=xcbincludedir xcb-proto`
{ $as_echo "$as_me:$LINENO: result: $XCBPROTO_XCBINCLUDEDIR" >&5
$as_echo "$XCBPROTO_XCBINCLUDEDIR" >&6; }
and the result is /usr/X11R7/share/xcb
Then in the src/Makefile, the first action is to create symlinks to xml
file and then run a python script :
ln -s -f /usr/X11R7/share/xcb/xproto.xml xproto.xml
/usr/bin/python ./c_client.py
-p /usr/X11R7/lib/python2.6/site-packages /usr/X11R7/share/xcb/xproto.xml
The problem is that the link should point to
$root/usr/X11R7/share/xcb/xproto.xml and the python script should use
this file.
What is the best way to change XCBPROTO_XCBINCLUDEDIR ? A patch to the
configure file ?
Regards,
Thomas
Le dimanche 23 août 2009 à 12:52 +0200, Thomas Jourdan a écrit :
> Hi
>
> I am cross-building a generic i486 target. My host is ubuntu 9.04 (64
> bits). The build fails on X11 stuffs, like libxcb, libx11 packages...
>
> I tracked a little the problem and the configure stage of some packages
> test for the presence of files. For example :
> - libxcb tests for /usr/X11R7/share/xcb/xproto.xml
> - libx11 tests for /usr/X11R7/include/X11/keysymdef.h
>
> Those files are provided by xproto, and are present in the $root
> directory but the configure scripts tests paths which point to host
> files. I didn't find a way to tell the configure script an alternative
> path.
>
> Shouldn't a wrapper handle this and add the $root directory as a
> prefix ? Isn't is automatic ? How can I add such a wrapper ?
>
> Regards,
> Thomas
>
>
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [email protected] with a subject of: unsubscribe t2
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
