aboutsummaryrefslogtreecommitdiffstats
path: root/lib/div64.c
diff options
context:
space:
mode:
authorSam Ravnborg <sam@mars.(none)>2005-07-14 20:22:39 +0000
committerSam Ravnborg <sam@mars.(none)>2005-07-14 20:22:39 +0000
commitd80e22460968ec7986c82fd7d207ebe3de59e03d (patch)
tree2dfe27aab805fe70f91b0d3beb45d23b2837990e /lib/div64.c
parentc5f75eca120de6587e67a1951ce3e6912e2c6879 (diff)
downloadkernel_samsung_aries-d80e22460968ec7986c82fd7d207ebe3de59e03d.zip
kernel_samsung_aries-d80e22460968ec7986c82fd7d207ebe3de59e03d.tar.gz
kernel_samsung_aries-d80e22460968ec7986c82fd7d207ebe3de59e03d.tar.bz2
kbuild: Don't fail if include/asm symlink exists
From: Andreas Gruenbacher <agruen@suse.de> We're having the following situation: There are user-space applications that include kernel headers directly. With a completely unconfigured /usr/src/linux tree, including most headers fails because essential files are not there: include/asm include/linux/autoconf.h include/linux/version.h So we create these files. On the other hand, we want to use /usr/src/linux as read-only source for building kernels or additional modules. Now when building a kernel with a separate output directory (O=), there is a check in the main makefile for the include/asm symlink. There is no real need for this check: if we ensure that $(objdir)/include/asm is always created as the patch does, $(srctree)/include/asm becomes irrelevant. Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Diffstat (limited to 'lib/div64.c')
0 files changed, 0 insertions, 0 deletions