On Tue, Aug 05, 2008 at 11:06:15PM +0100, Russell King wrote: > Currently, I know Linus' tree builds fine for most ARM platforms (thanks > to the ARM kautobuild project.) However, I'm seeing unexpected build > failures that don't make sense from the linux-next project. And the expression "oh bugger" comes to mind. The breakage in linux-next is because of 2e57d051160dd61776461637f767df19036b1186 and ea35455e0dc17d732436a5b98bd511cab64eb10e. During the last fortnight, I'd moved the "easy to move" ARM headers from include/asm-arm to arch/arm/include/asm. This means that, unknown to me, the symlink was no longer being created. That didn't get picked up in my testing, because I always build using O= builds into already existing object trees, which of course all have the symlink in place. This doesn't affect kautobuild because that always builds trees without using the O= facility. The question is what to do about it. Given the size of the task, I'm currently of the opinion that we're moving things around in the wrong order, and 4baa9922430662431231ac637adedddbb0cfb2d7 should be reverted until we've moved all the other ARM headers (in asm/arch and asm/plat-*) first. Maybe even leaving this until the next merge window now that -rc2 is out would be a good idea. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
