From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Tue, 14 Feb 2017 20:21:16 +0100 Subject: [Buildroot] Analysis of build results for 2017-02-13 In-Reply-To: <20170214161059.6a096f81@free-electrons.com> (Thomas Petazzoni's message of "Tue, 14 Feb 2017 16:10:59 +0100") References: <20170214072856.3AE8320B8C@mail.free-electrons.com> <20170214142725.1b9e98ae@free-electrons.com> <87lgt8kepo.fsf@dell.be.48ers.dk> <20170214161059.6a096f81@free-electrons.com> Message-ID: <87h93wk28j.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Thomas" == Thomas Petazzoni writes: > Hello, > On Tue, 14 Feb 2017 15:51:47 +0100, Peter Korsgaard wrote: >> Yes, I believe so (this failures are with gcc 6.x). I had a quick look >> yesterday, and our synergy package is ancient. It seems to have moved to >> github and changed quite a bit since then. >> >> https://github.com/symless/synergy/ >> >> The last release in the 1.3.x series is 1.3.8. I'll take a look and see >> if that has fixed this issue. > See: > [PATCH 1/1] package/synergy: bump to version 1.8.5 > on the mailing list. But that's a rather big update, with somewhat > scary things. Ahh yes. I was looking for something smaller/less risky for 2017.02 though. I see this patch is marked as rejected. Do you know why/by who? https://patchwork.ozlabs.org/patch/703714/ -- Bye, Peter Korsgaard