From: Jan Beulich <jbeulich@suse.com>
To: gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-x86_64-m64, revision 4814632e69636177b71b8d091009a0ec614916ec
Date: Fri, 17 Jan 2020 11:54:00 -0000 [thread overview]
Message-ID: <80b56bb1-ad16-7785-84c4-59f843791673@suse.com> (raw)
In-Reply-To: <E1isP3u-000657-62@gdb-buildbot.osci.io>
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
next prev parent reply other threads:[~2020-01-17 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 10:38 Oh dear. I regret to inform you that commit 4814632e69636177b71b8d091009a0ec614916ec might be unfortunate gdb-buildbot
2020-01-17 10:41 ` Breakage on builder Fedora-x86_64-cc-with-index, revision 4814632e69636177b71b8d091009a0ec614916ec gdb-buildbot
2020-01-17 10:55 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2020-01-17 11:54 ` Jan Beulich [this message]
2020-01-17 15:49 ` Simon Marchi
2020-01-17 11:19 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80b56bb1-ad16-7785-84c4-59f843791673@suse.com \
--to=jbeulich@suse.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox