lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 16 Jul 2014 23:39:30 -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 16

On Wed, Jul 16, 2014 at 11:14 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Nick,
>
> On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause <xerofoify@...il.com> wrote:
>>
>> Absolutely , I am using the latest kernel rc from git. I am using gcc
>> 4.8.3 and binutils 2.83.91.
>
> Then that has nothing to do with me ... I am the linux-next
> maintainer.  I just happen to use the same build test system as is also
> used to test Linus' tree (kisskb).  I hope you are looking at the right
> result pages for what you are testing.  The URL I gave you was for the
> linux-next builds, not Linus' tree.
>
>> In addition I am using  the default configurations as you are in less
>> I am doing it differently.
>> By the way xtensa-defconfig seems to fail because of binutils as I
>> discussed this with
>> the maintainers and they seemed to have tested it with a newer upstream binutils
>> then I am using and it succeeded it the linking failures I am seeing with it.
>
> Maybe we need per architecture minimum tools versions (instead of
> current global one).
>
> --
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au


That seems like a good idea. I am also curious if when there is a
build failure in
the mainline kernel if we can mail the logs to the maintainers of that
arch as if
we do it seems to get resolved much faster, usually in a day or two,
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