bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: test-rwlock1 failing on latest Fedora Rawhide
Date: Thu, 24 Jan 2019 08:57:49 +0000	[thread overview]
Message-ID: <20190124085749.GH12500@redhat.com> (raw)
In-Reply-To: <6764980.Kfckosteha@omega>


I see two patches that went into gnulib overnight.  I have now tried
compiling hivex with gnulib at commit 34881aff4043, and that seems to
have fixed the problem, thanks all.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html


  reply	other threads:[~2019-01-24  9:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 19:37 test-rwlock1 failing on latest Fedora Rawhide Richard W.M. Jones
2019-01-23 20:01 ` Bruno Haible
2019-01-23 20:45   ` Richard W.M. Jones
2019-01-23 21:03     ` Dmitry V. Levin
2019-01-23 21:14       ` Richard W.M. Jones
2019-01-23 22:09         ` Dmitry V. Levin
2019-01-23 22:24           ` Richard W.M. Jones
2019-01-23 22:38             ` Dmitry V. Levin
2019-01-24  3:18               ` Bruno Haible
2019-01-24  3:31                 ` Bruno Haible
2019-01-24  3:49                   ` Bruno Haible
2019-01-24  8:57                     ` Richard W.M. Jones [this message]
2019-01-24  8:50               ` Richard W.M. Jones
2019-01-23 21:17       ` Michael Hudson-Doyle

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190124085749.GH12500@redhat.com \
    --to=rjones@redhat.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.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).