From: Andrew Morton <akpm@linux-foundation•org>
To: Tony Breeds <tony@bakeyournoodle•com>
Cc: Peter Oberparleiter <peter.oberparleiter@de•ibm.com>,
linux-kernel@vger•kernel.org,
Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>,
linuxppc-dev@ozlabs•org,
Kernel Testers List <kernel-testers@vger•kernel.org>,
Sam Ravnborg <sam@ravnborg•org>
Subject: Re: [BUILD-FAILURE] 2.6.27-rc1-mm1 - allyesconfig build fails on powerpc
Date: Thu, 31 Jul 2008 23:12:06 -0700 [thread overview]
Message-ID: <20080731231206.80940fba.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080801052936.GZ20457@bakeyournoodle.com>
On Fri, 1 Aug 2008 15:29:36 +1000 Tony Breeds <tony@bakeyournoodle•com> wrote:
> On Thu, Jul 31, 2008 at 06:13:28PM +0530, Kamalesh Babulal wrote:
> > Hi Andrew,
> >
> > make allyesconfig with 2.6.27-rc1-mm1 kernel on powerpc fails with build error
>
> <snip>
>
> Turning off GCOV "fixes" this. Not really the best solution but at
> least it narrows doen the search effort.
Thanks.
> Peter,
> Can you have a look at how this can be fixed, if at all?
>
Am not terribly happy with the state of the gcov patches. They STILL
leave thousands of dead symlinks lying around after `make mrproper' and
generally seem to muck up the kbuild system a bit, although nothing
that a bit of Sam love wouldn't fix.
Plus it breaks the build on a few architectures (branch out of range,
mainly), but that's a fairly minor thing which could even be worked
around in Kconfig (disable the offending code if gcov is enabled)
next prev parent reply other threads:[~2008-08-01 6:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080731000354.24b55d5b.akpm@linux-foundation.org>
2008-07-31 12:43 ` [BUILD-FAILURE] 2.6.27-rc1-mm1 - allyesconfig build fails on powerpc Kamalesh Babulal
2008-08-01 5:29 ` Tony Breeds
2008-08-01 6:12 ` Andrew Morton [this message]
2008-08-01 15:40 ` Peter 1 Oberparleiter
2008-08-01 16:45 ` Sam Ravnborg
2008-08-01 15:44 ` Peter 1 Oberparleiter
2008-08-01 16:16 ` Kamalesh Babulal
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=20080731231206.80940fba.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=kernel-testers@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=peter.oberparleiter@de$(echo .)ibm.com \
--cc=sam@ravnborg$(echo .)org \
--cc=tony@bakeyournoodle$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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