qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Simeon Schaub <schaub@mit.edu>
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] explicitly link libqemuutil against rt
Date: Mon, 28 Feb 2022 16:08:05 +0000	[thread overview]
Message-ID: <YhzzZVt0KhjS1xST@redhat.com> (raw)
In-Reply-To: <949b0675-cbae-51dc-5a3b-d0215738279b@mit.edu>

On Mon, Feb 28, 2022 at 10:13:15AM -0500, Simeon Schaub wrote:
> We generally target glibc 2.12 in the Julia ecosystem, since CentOS 6 is
> still quite common in the HPC community.

Oh wow, we dropped RHEL/CentOS 6 support a very long time ago for QEMU,
and also dropped RHEL-7 last year.

FWIW, our platform target policy is set out here:

   https://www.qemu.org/docs/master/about/build-platforms.html

Currently RHEL-8 is the oldest RHEL we support since RHEL-7
also dropped out under the rule

  "Support for the previous major version will be dropped
   2 years after the new major version is released"

I'm surprised you didn't have to patch lots of other aspects of QEMU,
since a system targetting glibc 2.12 would be likely to have a GCC
version that we explicitly block use of at build time, as well as
other outdated 3rd party libraries we check min versions of in
configure.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      parent reply	other threads:[~2022-02-28 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  4:16 [PATCH] explicitly link libqemuutil against rt Simeon Schaub
2022-02-28 14:15 ` Peter Maydell
2022-02-28 14:38   ` Daniel P. Berrangé
2022-02-28 15:12     ` Peter Maydell
2022-02-28 15:13     ` Simeon Schaub
2022-02-28 15:17       ` Peter Maydell
2022-02-28 15:29         ` Simeon Schaub
2022-02-28 16:08       ` Daniel P. Berrangé [this message]

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=YhzzZVt0KhjS1xST@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=schaub@mit.edu \
    /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 NNTP newsgroup(s).