From: "Luck, Tony" <tony.luck@intel.com>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: new asm-offsets.h patch problems
Date: Mon, 12 Sep 2005 14:02:29 -0700 [thread overview]
Message-ID: <200509122102.j8CL2TW1021292@agluck-lia64.sc.intel.com> (raw)
I ran a loop of:
$ make mrproper
$ cp arch/ia64/configs/bigsur_defconfig .config
$ yes '' | make oldconfig
$ make -d V=1 prepare
until I had a success and a fail case. Then diffed the output from the
make -d V=1 prepare part. The successful one has the "<", the failed
one has the ">".
I editted off the start of the diff, where the only differences are the
process ids and addresses. Here's the output from "prepare0" to the
end of file. Note the stuttering "Putting childPutting child" in the
successful case, and that two processes 5577 and 5578 were forked in
the succesful case, while only one was started in the failing case.
Then after the reaping, the successful case decides that it must do
a remake of include/asm-ia64/asm-offsets.h, while the failing case
doesn't. The immediately preceeding lines to this pronouncement in
both cases are:
Finished prerequisites of target file `include/asm-ia64/asm-offsets.h'.
Prerequisite `arch/ia64/kernel/asm-offsets.s' is newer than target `include/asm-ia64/asm-offsets.h'.
Prerequisite `Kbuild' is older than target `include/asm-ia64/asm-offsets.h'.
Just in case this is a "make" issue, here's the version information:
$ make --version
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
85410,85411c85408,85409
< Putting child 0x60000000001549d0 (prepare0) PID 5576 on the chain.
< Live child 0x60000000001549d0 (prepare0) PID 5576
---
> Putting child 0x6000000000155b60 (prepare0) PID 6366 on the chain.
> Live child 0x6000000000155b60 (prepare0) PID 6366
87593c87591,87592
< Putting childPutting child 0x600000000003ad40 (arch/ia64/kernel/asm-offsets.s) PID 5577 on the chain.
---
> Putting child 0x600000000003adb0 (arch/ia64/kernel/asm-offsets.s) PID 6367 on the chain.
> Live child 0x600000000003adb0 (arch/ia64/kernel/asm-offsets.s) PID 6367
87595,87598c87594,87595
< 0x600000000003ad40 (arch/ia64/kernel/asm-offsets.s) PID 5577 on the chain.
< Live child 0x600000000003ad40 (arch/ia64/kernel/asm-offsets.s) PID 5577
< Reaping winning child 0x600000000003ad40 PID 5577
< Live child 0x600000000003ad40 (arch/ia64/kernel/asm-offsets.s) PID 5578
---
> Reaping winning child 0x600000000003adb0 PID 6367
> Live child 0x600000000003adb0 (arch/ia64/kernel/asm-offsets.s) PID 6368
87601,87602c87598,87599
< Reaping winning child 0x600000000003ad40 PID 5578
< Removing child 0x600000000003ad40 PID 5578 from chain.
---
> Reaping winning child 0x600000000003adb0 PID 6368
> Removing child 0x600000000003adb0 PID 6368 from chain.
87650,87657c87647
< Must remake target `include/asm-ia64/asm-offsets.h'.
< Putting child 0x600000000003ad40 (include/asm-ia64/asm-offsets.h) PID 5584 on the chain.
< Live child 0x600000000003ad40 (include/asm-ia64/asm-offsets.h) PID 5584
< mkdir -p include/asm-ia64/; cat arch/ia64/kernel/asm-offsets.s | (set -e; echo "#ifndef __ASM_OFFSETS_H__"; echo "#define __ASM_OFFSETS_H__"; echo "/*"; echo " * DO NOT MODIFY."; echo " *"; echo " * This file was generated by /home/aegl/bigsur/Kbuild"; echo " *"; echo " */"; echo ""; sed -ne "/^->/{s:^->\([^ ]*\) [\$#]*\([^ ]*\) \(.*\):#define \1 \2 /* \3 */:; s:->::; p;}"; echo ""; echo "#endif" ) > include/asm-ia64/asm-offsets.h
< Got a SIGCHLD; 1 unreaped children.
< Reaping winning child 0x600000000003ad40 PID 5584
< Removing child 0x600000000003ad40 PID 5584 from chain.
< Successfully remade target file `include/asm-ia64/asm-offsets.h'.
---
> No need to remake target `include/asm-ia64/asm-offsets.h'.
87662,87663c87652,87653
< Reaping winning child 0x60000000001549d0 PID 5576
< Removing child 0x60000000001549d0 PID 5576 from chain.
---
> Reaping winning child 0x6000000000155b60 PID 6366
> Removing child 0x6000000000155b60 PID 6366 from chain.
87668,87671d87657
< ^[]0;aegl@linux-t10:~/bigsur\a[aegl@linux-t10 bigsur]$ w\b \b
< ^[]0;aegl@linux-t10:~/bigsur\a[aegl@linux-t10 bigsur]$ exit
<
< Script done on Mon 12 Sep 2005 11:37:57 AM PDT
next reply other threads:[~2005-09-12 21:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 21:02 Luck, Tony [this message]
2005-09-12 23:17 ` Tony Luck
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 0:14 Luck, Tony
2005-09-12 16:00 Luck, Tony
2005-09-12 16:50 ` Al Viro
2005-09-12 19:01 ` Sam Ravnborg
2005-09-12 18:59 ` Sam Ravnborg
2005-09-13 0:08 ` Peter Chubb
2005-09-11 21:48 Luck, Tony
2005-09-11 22:07 ` Sam Ravnborg
2005-09-11 20:39 Luck, Tony
2005-09-11 21:36 ` Sam Ravnborg
2005-09-11 14:54 Luck, Tony
2005-09-11 6:07 Luck, Tony
2005-09-11 7:45 ` Sam Ravnborg
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=200509122102.j8CL2TW1021292@agluck-lia64.sc.intel.com \
--to=tony.luck@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®