From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Bug] 2.5.25 build as one user and install as root
Date: Sun, 07 Jul 2002 23:25:32 +0200 [thread overview]
Message-ID: <3D28B1CC.9070002@oracle.com> (raw)
In-Reply-To: 30159.1025956852@ocs3.intra.ocs.com.au
Keith Owens wrote:
> On Sat, 06 Jul 2002 13:28:06 +0200,
> Alessandro Suardi <alessandro.suardi@oracle.com> wrote:
>
>>Keith Owens wrote:
>>
>>>2.5.25 existing build system has a nasty bug. Build as one user then
>>>make install as root. It does supurious recompiles of some files and
>>>leaves them owned as root. All of these files are now owned by root
>>>and cause problems when the build user wants to rebuild.
>>
>>Doesn't happen for me.
>
>
> Check include/linux/compile.h after building as yourself and after
> installing as root. make install goes
>
> bzImage -> setup.o -> compile.h -> scripts/mkcompile_h ->
> #define LINUX_COMPILE_BY \"`whoami`\"
Keith Owens wrote:
> On Sat, 06 Jul 2002 13:28:06 +0200,
> Alessandro Suardi <alessandro.suardi@oracle.com> wrote:
>
>>Keith Owens wrote:
>>
>>>2.5.25 existing build system has a nasty bug. Build as one user then
>>>make install as root. It does supurious recompiles of some files and
>>>leaves them owned as root. All of these files are now owned by root
>>>and cause problems when the build user wants to rebuild.
>>
>>Doesn't happen for me.
>
>
> Check include/linux/compile.h after building as yourself and after
> installing as root. make install goes
>
> bzImage -> setup.o -> compile.h -> scripts/mkcompile_h ->
> #define LINUX_COMPILE_BY \"`whoami`\"
>
> whoami is different when you compile as one user then install as
> another.
>
Hey, give me some credit :)
[asuardi@dolphin linux]$ /bin/pwd
/usr/local/src/linux-2.5.25/include/linux
[asuardi@dolphin linux]$ cat compile.h
/* This file is auto generated, version 1 */
#define UTS_MACHINE "i386"
#define UTS_VERSION "#1 Sat Jul 6 02:27:10 CEST 2002"
#define LINUX_COMPILE_TIME "02:27:10"
#define LINUX_COMPILE_BY "asuardi"
#define LINUX_COMPILE_HOST "dolphin"
#define LINUX_COMPILE_DOMAIN ""
#define LINUX_COMPILER "gcc version 3.1"
I'm saying "doesn't happen for me" because it doesn't happen.
I've been compiling kernel as non-root (and well, of course
installing as root) since 1996.
I'll admit I checked only the files I cut'n'pasted last mail,
well let's be honest then...
[asuardi@dolphin linux]$ /bin/pwd
/usr/local/src/linux-2.5.25
[asuardi@dolphin linux]$ find . -user root -print
[asuardi@dolphin linux]$
See, *no* root-owned files here. Usual process is
* save previous kernel's .config
* zap previous kernel tree
* untar the previous kernel tree in /usr/local/src
* patch -p1 it with current kernel patch
* create new kernel tarball
* copy over saved .config
* make oldconfig
* make dep; make clean; make bzImage; make modules
* (wait for next kernel patch ;)
Ciao,
--alessandro
"my actions make me beautiful / and dignify the flesh"
(R.E.M., "Falls to Climb")
next prev parent reply other threads:[~2002-07-07 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 8:35 [Bug] 2.5.25 build as one user and install as root Keith Owens
2002-07-06 11:28 ` Alessandro Suardi
2002-07-06 12:00 ` Keith Owens
2002-07-07 21:25 ` Alessandro Suardi [this message]
2002-07-08 1:22 ` Keith Owens
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=3D28B1CC.9070002@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox