problems with several patches
Hello, I'm building XFree86 4.6+patches on a RedHat 7.2 basis (yes, I know this is OLD). The following patches are causing errors : 1) 4.6.99.3-4.6.99.4.diff.bz2 : the xterm binary is not created There is no install:: line for xterm in the Makefile. 2) 4.6.99.23-4.6.99.24.diff.bz2 : compilation error for ftfuncs.c (freetype) : ftfuncs.c:45:10: #include expects FILENAME or FILENAME ftfuncs.c:46:10: #include expects FILENAME or FILENAME ftfuncs.c:47:10: #include expects FILENAME or FILENAME ftfuncs.c:48:10: #include expects FILENAME or FILENAME ftfuncs.c:49:10: #include expects FILENAME or FILENAME ftfuncs.c:50:10: #include expects FILENAME or FILENAME ftfuncs.c:51:10: #include expects FILENAME or FILENAME ftfuncs.c:52:10: #include expects FILENAME or FILENAME The error seems to come from several include lines ; here is the first one : #include FT_FREETYPE_H FT_FREETYPE_H (and the other macros) should be expanded to a filename, but doesn't ... 3) 4.6.99.23-4.6.99.24.diff.bz2 : missing layer.h file installing driver SDK in programs/Xserver/miext/layer/module... make[5]: Entering `/home/rpm/BUILD/XFree86-4.6.0/xc/programs/Xserver/miext/layer/module' install -c liblayer.a /home/rpm/tmp/XFree86-4.6.0-root/usr/X11R6/lib/Server/modules/. install -c -m 0444 layer.h /home/rpm/tmp/XFree86-4.6.0-root/usr/X11R6/lib/Server/include install: cannot stat `layer.h': No such file or directory In fact, both miext/layer/Makefile and miext/layer/module/Makefile try to install layer.h But the file in only in the first directory. Loïc
Re: XFree86 driver
Thanks, Marc. Is there no way in which socket() system call and other socket related API be implemented in a XFree86 input driver? When I try to implement the same, while loading the driver module the XFree86 module loader gives Unresolved symbol for each of the functions. Even dlopen() cannot be used as it results in the same error. Could you provide any way to resolve the above issue, as we would like the driver to take input from socket (i.e. from a remote touchscreen). Thank you. Marc Aurele La France [EMAIL PROTECTED] wrote: On Sat, 9 Jun 2007, Pankaj S wrote: Has anyone implemented sockets in an XFree86 input driver? Please let me know. Not to my knowledge. Marc. +--+--+ | Marc Aurele La France | work: 1-780-492-9310 | | Academic Information and | fax: 1-780-492-1729 | | Communications Technologies | email: [EMAIL PROTECTED] | | 352 General Services Building +--+ | University of Alberta | | | Edmonton, Alberta | Standard disclaimers apply | | T6G 2H1 | | | CANADA | | +--+--+ XFree86 developer and VP. ATI driver and X server internals. ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel - Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool.
Re: XFree86 driver
On Mon, 11 Jun 2007, Pankaj S wrote: Thanks, Marc. Is there no way in which socket() system call and other socket related API be implemented in a XFree86 input driver? When I try to implement the same, while loading the driver module the XFree86 module loader gives Unresolved symbol for each of the functions. Even dlopen() cannot be used as it results in the same error. Modules are deliberately only allowed to call a restricted list of system calls which are known to work (the same way ?) on (all ?) operating systems that XFree86 runs on. The idea is (or at least was) that *binary* modules could be built on one OS and run on any other. dlopen() is definitely not allowed and I don't think that system() is either. To add a system call you would need to add them to every server that your module is to work with. *If* you were to do that it would be best to collaborate with Xorg as well as XFree86. Could you provide any way to resolve the above issue, as we would like the driver to take input from socket (i.e. from a remote touchscreen). x2x ( ftp://gatekeeper.dec.com/pub/DEC/SRC/x2x/x2x-1.27.tar.gz ) uses the XTEST extension to drive the input of a remote X display. Could you run something on the machine with the touchscreen which uses XTEST to send data to the display you were writing an input driver for ? ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
