Olaf hering suggested to remove the -fsigned-char gcc flag from the compiler options. Not all BE platforms use it.
Created attachment 2388 [details] [review] See above.
This still needs to be tested - but since most platforms don't seem to require it we may savely leave it out. I frankly don't see why this should be relevant for BE only anyway.
2005-04-11 Egbert Eich <eich-at-freedesktop-dot-org> * config/cf/linux.cf: Removing the compiler flag -fsigned-char which is only used for a few BE platforms. This still needs some testing - which can only be done when in the tree, but since most platforms don't need I strongly assume it's not needed. Ticket remains open for discussion (Bugzilla #2964). Committed. Not closing ticket for further discussion.
Indeed, it has nothing to do with big endian - ARM is little endian I think. The reason why this was traditionally necessary is that char is unsigned by default on these architectures, and code coming from other architectures tends to assume that char is signed by default. That said, it would definitely be nice if all those bugs have been fixed, but we need to watch out for odd problems getting reported on these architectures.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Nobody seems to have reported any problems in the intervening three years. Closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.