On Mon, Dec 29, 2008 at 03:43:52PM +0530, Kedar Sovani wrote:
#include_next is not understood by the compiler, and hence it gives
(I don't understand why this is not seen in x86 builds, comments?)
Probably because the binary package in the archive was built with
some older gcc version, or something like that. Try rebuilding the
package on x86 on a fully updated root fs and see if it still happens?
%patch0 -p1 -b .aconf262
+%patch1 -p1 -b .include-next-fix
Don't make patches dependent on the build environment (I think there
is a rule forbidding doing what you're doing here).