[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130722100550.553af77b06c5de6a2471a47b@canb.auug.org.au>
Date: Mon, 22 Jul 2013 10:05:50 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Mark Brown <broonie@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree
(sound-asoc tree related)
HI Mark,
On Fri, 19 Jul 2013 11:02:37 +0100 Mark Brown <broonie@...nel.org> wrote:
>
> On Fri, Jul 19, 2013 at 01:52:53PM +1000, Stephen Rothwell wrote:
>
> > After merging the final tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
>
> What goes into the final tree that might cause such breakage that didn't
> appear in the earlier merges or is this additional testing that isn't
> performed on the earlier merges?
From my daily release message:
"You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc,
sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary."
The powerpc allyesconfig catches quite a few build problems.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists