Skip to main content

CROSS COMPILING X11 FOR ARM Board

STEPS FOR CROSS COMPILING X11 FOR ARM
Go to /usr/X11R6/lib in my linux PC.

1) install ARM toolchain, If not installed
2) Get x11 source from http://www.x.org/
3) extract all the tar files, using tar -xvzf
4) edit cross.def and host.def files, in cross.def set the paths
of tool chain in host.def file set crossCompile to YES and
DoLoadableServer to NO
5) make shadow directory "build" and link to xc "lndir ../xc"
6) run Make World


error: linux_vm86.c 281 impossible constraint in 'asm'
268 res might be used uninitialized in this function.
fix:comment line 281,
set res=0


error: implicit decleration of function 'SET_FLAG'
fix: comment line 111 in
programs/Xserver/hw/xfree86/os-support/linux/int10/helper_exec.c


error:Undefined reference to XF86VidModeQueryVersion in glxinfo
And glxgears
Undefined reference to XF86VidModeQueryVersion in xdriinfo
fix:download libXxf86vm.so.1.0 into our armtoolchain lib path
and make softlinks

ln -s libXxf86vm.so.1.0 libXxf86vm.so
ln -s libXxf86vm.so.1.0 libXxf86vm.so.1

error:X_cursor.cfg command not found.
fix:

copied all the binaries from cvs in our
arm-tools-chain bin folder...didnt work

copied libXcursor.so.1.0.2 from cvs in our arm-tools-chain
and made links

ln -s libXcursor.so.1.0.2 libXcursor.so.1
ln -s libXcursor.so.1.0.2 libXcursor.so
...still didnt work

copied xcursor.pc in pkgconfig of toolchain.

looks like xcursorgen is missing .
got it from debian.still didnt work.

copied xcursorgen from programs/xcursorgen/ to tool chain
still didnt work.

export XCURSORGEN=/usr/X11R6/bin/xcursorgen
!!! WORKED !!!


Total compilation time with "Make World" is 20 minutes.

after compilation it prints a message:
"Full build of Release 6.8 complete."

error: while doing make install got the error in fonts:
"/bin/sh -b: command not found"

workaround:
removed "models" folder from Makefile at
"programs/Xserver/XpConfig/C/print/Makefile
fix:Open the makefile in Xserver/XpConfig/C/print/models/XXX/fonts/Makefile
and then set MKFONTSCALE=$(XBINDIR)/mkfontscale below XBINDIR on line
no around 389.

Comments

Anonymous said…
I am also trying to cross-compile Xserver on my ARM board.
Could you please take more detail on each step: which files used, commands,...
Thanks in advance.

Popular posts from this blog

Dotnet, .Net 3.5, 2.0, C# Interview Questions

Few questions on dotnet, C# 2.0, 3.5 On Object oriented concepts 1)What is inheritance with e.g 2)What is polymorphism -function overloading -Function overriding -virtual keyword use -Static keyword and use -Abstract classes -Interface -Object 3)What is threading and how do we use in realtime application(cognizant) 4)What is threadpooling, lock, monitor(write code sample) 5)Architecture of current project 6)Session state, diffrent types of state management. 7)What is Application_Start, how it works. 8)Type of authentication in asp.net 9)How to configure ASP.NET application. 10) What is Impersonation. 11) What is WebService, WSDL, UDDI, Discovery, asmx files. 12) How to implement WebService and use it. 13) When to use WebServices. 14) WPF, how to implement(BOA) 15) Testing concvepts. 16) Test attributes 17) Flow of Automation Test Method execution 18) Features of dotnet 3.5 19) CLR, garbage collection 20) Finally block 21) Manifest, Metadata, MSIL 22) Assemblies, Type of assemblies, str...

Remote debugging for ARM target board

Remote debugging for ARM target board With GDB one can both trace and modify code and data flow, and otherwise analyze the behavior of code, without explicitly changing any of it. Rather than run a full-blown instance of GDB on the target platform, you can use GDBserver , a program that lets you run GDB on a different machine than the one on which your program is running. The advantage of using GDBserver is that it needs just a fraction of the target resources that GDB consumes, because it implements only the low-level functionality of the debugger -- namely setting breakpoints and accessing the target processor registers and read/write application memory. GDBserver takes control of the application being debugged, and then waits for instructions from a remote instance of GDB running on a development workstation. Remote target needs to have debugging stub (gdbserver), The gdbserver is also referred to as the 'stub' and must be cross-compiled for that targ...