lkml.org 
[lkml]   [2008]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [BUILD-FAILURE] 2.6.27-rc1-mm1 - allyesconfig build fails on powerpc
    From
    Date
    Andrew Morton <akpm@linux-foundation.org> wrote on 01.08.2008 08:12:06:
    > 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'


    This is caused by patch

    gcov-create-links-to-gcda-files-in-build-directory.patch

    which can be simply removed as it is no longer needed since patch

    gcov-add-gcov-profiling-infrastructure-revert-link-changes.patch

    has been added to -mm.

    > and
    > generally seem to muck up the kbuild system a bit, although nothing
    > that a bit of Sam love wouldn't fix.

    Hm, by now the only change to kbuild is the addition of gcc options
    -fprofile-arcs/-ftest-coverage depending on the respective config
    symbols. If there is anything else that should be changed, please
    let me know.

    > 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)

    Some of the problems caused/uncovered by enabling gcov profiling for
    a kernel build on some architectures simply cannot be fixed by a change
    to the kernel patch itself. I'm wondering if it would be possible
    to disable this configuration option when specifying allyesconfig. That
    way at least generic testing wouldn't be affected.


    Regards,
    Peter


    \
     
     \ /
      Last update: 2008-08-01 17:45    [W:3.611 / U:0.164 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site