Date:	Sun, 13 Jul 2014 00:08:48 -0400
From:	Nick Krause <xerofoify@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Jul 11

On Sat, Jul 12, 2014 at 6:26 PM, Nick Krause <xerofoify@...il.com> wrote:
> On Fri, Jul 11, 2014 at 3:18 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi all,
>>
>> Changes since 20140710:
>>
>> My fixes tree contains:
>>         powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
>>
>> The tty.current tree gained a build failure so I used the version from
>> next-20140710.
>>
>> The irqchip tree gained a conflict against the arm64 tree.
>>
>> The staging tree lost its build failure and gained a conflict against
>> the tty tree.
>>
>> Non-merge commits (relative to Linus' tree): 5114
>>  4474 files changed, 191199 insertions(+), 226003 deletions(-)
>>
>> ----------------------------------------------------------------------------
>>
>> I have created today's linux-next tree at
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
>> are tracking the linux-next tree using git, you should not use "git pull"
>> to do so as that will try to merge the new linux-next release with the
>> old one.  You should use "git fetch" and checkout or reset to the new
>> master.
>>
>> 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 and a
>> multi_v7_defconfig for arm. After the final fixups (if any), it is also
>> built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
>> allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
>> defconfig.
>>
>> Below is a summary of the state of the merge.
>>
>> I am currently merging 222 trees (counting Linus' and 30 trees of patches
>> pending for Linus' tree).
>>
>> Stats about the size of the tree over time can be seen at
>> http://neuling.org/linux-next-size.html .
>>
>> Status of my local build tests will be at
>> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
>> advice about cross compilers/configs that work, we are always open to add
>> more builds.
>>
>> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
>> Gortmaker for triage and bug fixes.
>>
>> --
>> Cheers,
>> Stephen Rothwell                    sfr@...b.auug.org.au
>>

> I am been trying your tests for a while. Seems most of your failing
> tests work for me.
> Can you test a newer compiler in the 4.8 release series for gcc to see
> if this fixes your
> issues.
> Cheers Nick
I am also attaching logs of build I have that are succeeding to help
you.Furthermore I run the builds in two steps listed below using
compilers for
Ubuntu 14.04 and Fedora 20 turned into dpkgs to work with Debian
distros.Below are the steps.
1. make ARCH=x y_defconfig
2.ARCH= x CROSS_COMPILE=z make -j 8 2> error_file
x = cpu architecture  I am building
y=configuration I am building
z= gcc I am builds this architecture
error_file = file I am tracing errors and warnings to send if build
fails to maintainers of that architecture
If you have any other questions please ask me.
Cheers Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists