mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: pradeep singh rautela <rautelap@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q]Adding src files to 2.6.18 kernel and build failure query
Date: Tue, 11 Sep 2007 08:19:52 +0200	[thread overview]
Message-ID: <20070911061952.GA3429@uranus.ravnborg.org> (raw)
In-Reply-To: <6bc632150709102247s3071c60jcddf8f88c8f2bc10@mail.gmail.com>

On Tue, Sep 11, 2007 at 11:17:48AM +0530, pradeep singh rautela wrote:
> On 9/10/07, Sam Ravnborg <sam@ravnborg.org> 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

  reply	other threads:[~2007-09-11  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10 16:05 pradeep singh rautela
2007-09-10 16:15 ` Jan Engelhardt
2007-09-10 16:38 ` Sam Ravnborg
2007-09-11  5:47   ` pradeep singh rautela
2007-09-11  6:19     ` Sam Ravnborg [this message]
2007-09-11  6:23       ` pradeep singh rautela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070911061952.GA3429@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rautelap@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome