From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where does kernel/resource.c.1 file come from?
Date: Tue, 25 Jul 2006 17:33:33 +0200 [thread overview]
Message-ID: <200607251733.38467.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <20060725151520.GA15681@mars.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Am Dienstag, 25. Juli 2006 17:15 schrieb Sam Ravnborg:
> On Tue, Jul 25, 2006 at 03:54:45PM +0200, Rolf Eike Beer wrote:
> > Hi,
> >
> > I'm playing around with my local copy of linux-2.6 git tree. I'm building
> > everything to a separate directory using O= to keep "git status" silent.
> >
> > After building I sometimes find a file kernel/resource.c.1 in my git tree
> > that doesn't really belong there. Who is generating this file, for what
> > reason and why doesn't it get created in my output directory?
>
> I have never seen this myself so a bit puzzled???
> Is it only kernel/resource.c that generates the .1 file - or is it
> somethign that is general?
No, it is always kernel/resource.c.1
> Can you also try to make sure that this file is generated as part of the
> build process. git status before and after should do it.
I've never seen anything but this file beside my local changes, which don't
affect the build process at all.
> If you can relaiably provoke it output of make V=1 would be usefull.
I'll try. Will probably take until tomorrow.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-25 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 13:54 Where does kernel/resource.c.1 file come from? Rolf Eike Beer
2006-07-25 15:15 ` Sam Ravnborg
2006-07-25 15:33 ` Rolf Eike Beer [this message]
2006-07-28 14:03 ` Rolf Eike Beer
2006-07-28 14:10 ` Sam Ravnborg
2006-08-04 13:03 ` Pavel Machek
2006-08-07 6:11 ` Rolf Eike Beer
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=200607251733.38467.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.