From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2184 invoked by alias); 17 Jan 2020 11:19:01 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 2158 invoked by uid 89); 17 Jan 2020 11:19:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-7.1 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_3,SPF_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mx2.suse.de Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 17 Jan 2020 11:18:50 +0000 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id EC85BAD73 for ; Fri, 17 Jan 2020 11:18:47 +0000 (UTC) Subject: Re: Breakage on builder Fedora-x86_64-m64, revision 4814632e69636177b71b8d091009a0ec614916ec To: gdb-patches@sourceware.org References: From: Jan Beulich Message-ID: <80b56bb1-ad16-7785-84c4-59f843791673@suse.com> Date: Fri, 17 Jan 2020 11:54:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-01/txt/msg00513.txt.bz2 On 17.01.2020 11:41, gdb-buildbot@sergiodj.net wrote: > Unfortunately it seems that there is a breakage on GDB. > > Commit title: 'x86: VPEXTRQ/VPINSRQ are unavailable outside of 64-bit mode' > Revision: 4814632e69636177b71b8d091009a0ec614916ec > > You can find more details below: Unfortunately the details lack any details. This way I can neither put it off, nor see about addressing it. > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > +++ The full log is too big to be posted here. > +++ These are the last 100 lines of it. I guess I can see why this is, but this way the only sign of a failures is ... > make: *** [Makefile:853: all] Error 2 > program finished with exit code 2 ... this. Hints as to what to do, or where to find the full build log, appreciated. Jan