Re: Fw: [AL] Cross-compiling for arm-linux with only framebuffer support

[Eric B. <ebo...@li...>]

> Well it certainly gets a lot further now!  It compiles examples!!!

Wunderbar! :-)

> But ... (there's always a but)
>
> First "but" is the following when making documentation:
>
> docs/makedoc -ascii docs/txt/ahack.txt docs/src/ahack._tx
> docs/makedoc: docs/makedoc: cannot execute binary file
> make: *** [docs/txt/ahack.txt] Error 126

Ok, let's disable it for now.  I've attached a new patch that supersedes all 
the previous ones.

> I tried running some of the examples on the arm.  ex3d ran fine.  ;-)

Encouraging.

> exmem gives "Shutting down Allegro due to signal #11" and I get the
> following written to stderr:
>
> pc : [<0002c25c>]    lr : [<00000000>]    Not tainted
> sp : bffffb78  ip : 0000013f  fp : bffffd98
> r10: 000000c8  r9 : 00068fc0  r8 : 00000140
> r7 : 00000140  r6 : 0007f2d0  r5 : 000001e0  r4 : 00000000
> r3 : 00000000  r2 : 401cd000  r1 : 000001e1  r0 : 401cd000
> Flags: nZCv  IRQs on  FIQs on  Mode USER_32  Segment user
> Control: 397F  Table: A18B4000  DAC: 00000015
>
> exsprite gives a similar error.

I can see a difference between ex3d and exmem, expsrite: the former uses

   if (set_gfx_mode(GFX_SAFE, 320, 200, 0, 0) != 0) {
      set_gfx_mode(GFX_TEXT, 0, 0, 0, 0);
      allegro_message("Unable to set any graphic mode\n%s\n", allegro_error);
      return 1;
   }

to set up the graphics mode, while the latters use

   if (set_gfx_mode(GFX_AUTODETECT, 320, 200, 0, 0) != 0) {
      if (set_gfx_mode(GFX_SAFE, 320, 200, 0, 0) != 0) {
	 set_gfx_mode(GFX_TEXT, 0, 0, 0, 0);
	 allegro_message("Unable to set any graphic mode\n%s\n", allegro_error);
	 return 1;
      }
   }

Could you see whether deleting the GFX_AUTODETECT line helps?

-- 
Eric Botcazou