public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Alan Modra <amodra@gmail.com>
Subject: Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, revision 09c78487342254de6a4498f8b3aa1f3f1d508898
Date: Wed, 11 Dec 2019 20:02:00 -0000	[thread overview]
Message-ID: <E1if8BI-0002Nw-Vr@gdb-buildbot.osci.io> (raw)
In-Reply-To: <09c78487342254de6a4498f8b3aa1f3f1d508898-master-breakage@gdb-build>

Unfortunately it seems that there is a breakage on GDB.

Commit title: 'Make bfd_get_8 return a bfd_vma like other bfd_get_* functions'
Revision: 09c78487342254de6a4498f8b3aa1f3f1d508898

You can find more details below:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


+++ The full log is too big to be posted here.
+++ These are the last 100 lines of it.

checking whether this system has an arbitrary file name length limit... yes
checking for closedir... yes
checking for d_ino member in directory struct... yes
checking for d_type member in directory struct... yes
checking whether alphasort is declared without a macro... yes
checking whether closedir is declared without a macro... yes
checking whether dirfd is declared without a macro... yes
checking whether fdopendir is declared without a macro... yes
checking whether opendir is declared without a macro... yes
checking whether readdir is declared without a macro... yes
checking whether rewinddir is declared without a macro... yes
checking whether scandir is declared without a macro... yes
checking for dirfd... yes
checking whether dirfd is declared... (cached) yes
checking whether dirfd is a macro... no
checking whether // is distinct from /... (cached) no
checking whether dup works... yes
checking whether dup2 works... yes
checking for error_at_line... yes
checking whether fcntl handles F_DUPFD correctly... yes
checking whether fcntl understands F_DUPFD_CLOEXEC... needs runtime check
checking whether fcntl is declared without a macro... yes
checking whether openat is declared without a macro... yes
checking whether fdopendir is declared... (cached) yes
checking whether fdopendir works... yes
checking for flexible array member... yes
checking whether conversion from 'int' to 'long double' works... yes
checking for working GNU fnmatch... yes
checking whether frexp works... yes
checking whether frexpl is declared... yes
checking whether frexpl() can be used without linking with libm... yes
checking whether frexpl works... yes
checking whether fstatat (..., 0) works... yes
checking whether getcwd handles long file names properly... yes
checking for getpagesize... yes
checking whether getcwd aborts when 4k < cwd_length < 16k... no
checking whether getdtablesize works... yes
checking whether getlogin_r works with small buffers... yes
checking whether program_invocation_name is declared... yes
checking whether program_invocation_short_name is declared... yes
checking whether __argv is declared... no
checking whether gettimeofday clobbers localtime buffer... no
checking for gettimeofday with POSIX signature... almost
checking glob.h usability... yes
checking glob.h presence... yes
checking for glob.h... yes
checking for GNU glob interface version 1... no
checking for library containing inet_ntop... none required
checking whether inet_ntop is declared... (cached) yes
checking whether INT32_MAX < INTMAX_MAX... yes
checking whether INT64_MAX == LONG_MAX... yes
checking whether UINT32_MAX < UINTMAX_MAX... yes
checking whether UINT64_MAX == ULONG_MAX... yes
checking whether isnan(double) can be used without linking with libm... yes
checking whether isnan(long double) can be used without linking with libm... yes
checking whether isnanl works... yes
checking for pthread_rwlock_t... yes
checking whether NAN macro works... yes
checking whether HUGE_VAL works... yes
checking whether acosf is declared without a macro... yes
checking whether acosl is declared without a macro... yes
checking whether asinf is declared without a macro... yes
checking whether asinl is declared without a macro... yes
checking whether atanf is declared without a macro... yes
checking whether atanl is declared without a macro... yes
checking whether cbrt is declared without a macro... yes
checking whether cbrtf is declared without a macro... yes
checking whether cbrtl is declared without a macro... yes
checking whether ceilf is declared without a macro... yes
checking whether ceill is declared without a macro... yes
checking whether copysign is declared without a macro... yes
checking whether copysignf is declared without a macro... yes
checking whether copysignl is declared without a macro... yes
checking whether cosf is declared without a macro... yes
checking whether cosl is declared without a macro... yes
checking whether coshf is declared without a macro... yes
checking whether expf is declared without a macro... yes
checking whether expl is declared without a macro... yes
checking whether exp2 is declared without a macro... yes
checking whether exp2f is declared without a macro... yes
checking whether exp2l is declared without a macro... yes
checking whether expm1 is declared without a macro... yes
checking whether expm1f is declared without a macro... yes
checking whether expm1l is declared without a macro... yes
checking whether fabsf is declared without a macro... yes
checking whether fabsl is declared without a macro... yes
checking whether floorf is declared without a macro... yes
checking whether floorl is declared without a macro... yes
checking whether fma is declared without a macro... yes
checking whether fmaf is declared without a macro... yes
checking whether fmal is declared without a macro... yes
checking whether fmod is declared without a macro... yes
checking whether fmodf is declared without a macro... yes
checking whether fmodl is declared without a macro... yes
checking whether frexpf is declared without a macro... yes
checking whether frexpl is declared without a macro... yes
checking whether hypotf is declared without a macro... yes
checking whether hypotl is declared without a macro... yes
checking whether ilogb is declared without a macro... yes

  parent reply	other threads:[~2019-12-11 20:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 19:56 Oh dear. I regret to inform you that commit 09c78487342254de6a4498f8b3aa1f3f1d508898 might be unfortunate gdb-buildbot
2019-12-11 19:56 ` Breakage on builder Ubuntu-Aarch64-m64, revision 09c78487342254de6a4498f8b3aa1f3f1d508898 gdb-buildbot
2019-12-11 20:02 ` gdb-buildbot [this message]
2019-12-11 20:07 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-12 11:02 ` Breakage on builder Fedora-i686, " gdb-buildbot
2019-12-12 11:07 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-12 11:09 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2019-12-12 11:13 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-12 11:16 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-12-12 11:21 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-12 11:38 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-12-12 11:39 ` Breakage on builder Fedora-x86_64-native-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=E1if8BI-0002Nw-Vr@gdb-buildbot.osci.io \
    --to=gdb-buildbot@sergiodj.net \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).