Re: [Q]Adding src files to 2.6.18 kernel and build failure query

From: Sam Ravnborg
Date: Tue Sep 11 2007 - 02:27:35 EST


On Tue, Sep 11, 2007 at 11:17:48AM +0530, pradeep singh rautela wrote:
> On 9/10/07, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote:
> [...]
> > > I added some .c files to a new dir under net/foo/ .
> > > Added corresponding .h files to a new dir under include/foo/
> > >
> > > Create a Kconfig and Makefile in net/foo/ directory.
> > > Added corresponding entries to Makefile and Kconfig in the net/ dir.
> > >
> > > I happily executed a make with a beaming face after selecting the foo
> > > option after doing a
> > > $make menuconfig.
> > >
> > > To my surprise i got this error :-
> > >
> > > make[1]: *** No rule to make target `arch/i386/kernel/vmlinux.lds',
> > > needed by `__build'. Stop
> >
> > Did the kernel build before you started adding your stuff?
> > It looks like you broke something non-obvious when adding your stuff since the
> > above failure should not happen just by adding a new directory under net/
>
> Went home and tried again. It builds fine in git repo, but again
> whenever i make an archive using git-archive --format=tar
> --prefix=linux-2.6.18/ HEAD | bzip2 > linux-2.6.18.tar.bz2 , i get the
> problem with this bzipped tree.
>
> I removed .gitignore file from the my git repo and added manually
> rules to .git/info/exclude instead. This did the trick and
> git-archiv'ing did not result in a broken bzipped tree.
>
> Perhaps i did something silly or may be something to do with git. ??

You where hit by a problem in the top-level .gitignore.
See commit: eaf729c8a8bfc9c7a5ff5659e3b2584bf2ef22e1

Use: git show eaf729c8a8bfc9c7a5ff5659e3b2584bf2ef22e1

This commit is most likely not in your tree.
It just do:
diff --git a/.gitignore b/.gitignore
index 8d15830..a232295 100644
--- a/.gitignore
+++ b/.gitignore
@@ -22,6 +22,7 @@
tags
TAGS
vmlinux*
+!vmlinux.lds.S
System.map
Module.symvers


Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/