From: Nick Alcock <nick.alcock@oracle.com>
To: Kamil Rytarowski <n54@gmx.com>
Cc: gdb-buildbot@sergiodj.net, Nick Alcock <nick.alcock@oracle.com>,
gdb-patches@sourceware.org
Subject: Re: Breakage on builder NetBSD-x86_64-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d
Date: Wed, 29 May 2019 12:51:00 -0000 [thread overview]
Message-ID: <87muj55sqd.fsf@esperi.org.uk> (raw)
In-Reply-To: <a70fc0ae-2d16-2059-b30b-15e06cc7cdfd@gmx.com> (Kamil Rytarowski's message of "Wed, 29 May 2019 07:51:42 +0200")
On 29 May 2019, Kamil Rytarowski told this:
> On 29.05.2019 06:26, gdb-buildbot@sergiodj.net wrote:
>> Unfortunately it seems that there is a breakage on GDB.
>>
>
> There is no off64_t on NetBSD as off_t is 64-bit.
>
> qsort_r is missing.
Working on it. (Other platforms don't have qsort_r() either: apparently
my utterly clear memory of using it on platforms as old as HP-UX 10.10
is a confabulation :( )
(I guess there's some configure magic I can use to #define off64_t off_t
on sufficiently capable systems...)
--
NULL && (void)
next prev parent reply other threads:[~2019-05-29 12:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 0:02 Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate gdb-buildbot
2019-05-29 0:02 ` Breakage on builder Solaris11-sparcv9-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d gdb-buildbot
2019-05-29 1:34 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-05-29 2:16 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Simon Marchi
2019-05-29 10:21 ` Rainer Orth
2019-05-29 12:46 ` Nix
2019-05-29 13:14 ` Andreas Schwab
2019-05-29 13:38 ` Rainer Orth
2019-05-29 14:18 ` Nick Alcock
2019-05-29 16:33 ` [PATCH] Fix a number of build problems found on Solaris and NetBSD (was Re: Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate) Nick Alcock
2019-05-29 18:22 ` Rainer Orth
2019-05-29 20:08 ` Nick Alcock
2019-05-29 20:34 ` Kamil Rytarowski
2019-05-29 21:46 ` Nick Alcock
2019-05-30 0:54 ` Sergio Durigan Junior
2019-05-30 7:14 ` Kamil Rytarowski
2019-05-30 9:35 ` Nick Alcock
2019-05-29 16:04 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Nick Alcock
2019-05-29 4:26 ` Breakage on builder NetBSD-x86_64-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d gdb-buildbot
2019-05-29 5:51 ` Kamil Rytarowski
2019-05-29 12:51 ` Nick Alcock [this message]
2019-05-29 23:31 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2019-05-30 0:13 ` Nick Alcock
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=87muj55sqd.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=n54@gmx.com \
/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