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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6bc632150709102247s3071c60jcddf8f88c8f2bc10@mail.gmail.com>
Date:	Tue, 11 Sep 2007 11:17:48 +0530
From:	"pradeep singh rautela" <rautelap@...il.com>
To:	"Sam Ravnborg" <sam@...nborg.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Q]Adding src files to 2.6.18 kernel and build failure query

On 9/10/07, Sam Ravnborg <sam@...nborg.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. ??

Thanks for the hint Sam.
--pradeep
--
pradeep singh rautela

"question = ( to ) ? be : ! be;"
                -- Wm. Shakespeare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/