el_pango
Member
Apologies for starting a new thread, but can someone out there in Pandora dev land attempt to download Allegro 4.2.3.1 (or 4.4.x, if you wish), unpack it, then in the directory where it got unpacked to, run 
	
	
	
		
 then 
	
	
	
		
 and finally 
	
	
	
		
, and post any errors you get here?
More specifically, I am trying to figure out why 'configure' seems to detect a lot of things just fine, but doesn't actually set or #define them and/or wondering if I've somehow incorrectly set up or hosed my dev environment, and am curious to see whether others will run into the same problems (to wit: 'configure' picks up on the presence of libpthread, the fact that we're small-endian, etc, but the defines Allegro uses to know this and compile the library accordingly aren't actually getting #define-d).
				
			
		Code:
	
	sh ./fix.sh unix
	
		Code:
	
	sh ./configure --disable-color8
	
		Code:
	
	make
	More specifically, I am trying to figure out why 'configure' seems to detect a lot of things just fine, but doesn't actually set or #define them and/or wondering if I've somehow incorrectly set up or hosed my dev environment, and am curious to see whether others will run into the same problems (to wit: 'configure' picks up on the presence of libpthread, the fact that we're small-endian, etc, but the defines Allegro uses to know this and compile the library accordingly aren't actually getting #define-d).
	