On Wed, Dec 31, 2003 at 03:44:17PM +0100, Marc Haber wrote: > On Wed, Dec 31, 2003 at 09:12:42AM -0500, Daniel Jacobowitz wrote: > > On Wed, Dec 31, 2003 at 11:21:11AM +0100, Marc Haber wrote: > > > Package: linux-kernel-headers > > > Version: 2.5.999-test7-bk-10 > > > Severity: wishlist > > > > > > Hi, > > > > > > when the package is built, there is no include/asm. This causes > > > /usr/include/asm to be used during package build, which breaks on > > > woody. This will probably cause interesting effects when packaging the > > > next kernel-headers version that has differing include/asm definitions. > > > > > > IMO, a symlink include/asm -> asm-$ARCH needs to be generated on > > > package build, otherwise building the test suite will fail. > > > > Please give more details. > > I am going to try. > > When building the package, the testsuite is built with something along > the lines of -I../include which points to include/asm in the source > package "root" directory. > > That directory doesn't have an include/asm symlink at this time of > building, causing "#include <asm/foo>" to pull in /usr/include/asm/foo > instead of ../include/asm-$ARCH/foo. This is not a problem on sid > since sid systems _currently_ have a compatible (identical?) file in > /usr/include, but fails on woody. And it's bound to fail when the > kernel headers are changed in a way that include/asm will differ. > > > I know that changes to asm-i386/ show up in the testsuite results so it > > works here. Perhaps a different version of debhelper is breaking some > > assumption? > > Probably, since I am talking woody here. > > If this doesn't help, I will give more explicit results when I have > again access to the build host.
The testsuite is built with: LOCAL_CFLAGS = -I $(shell pwd)/../debian/linux-kernel-headers/usr/include -I $(shell pwd)/../include If there is no asm dir in ../debian/linux-kernel-headers/usr/include then the package wasn't built right at all. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
