qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH for-4.0 1/7] configure: Add a test for the minim


From: Daniel P . Berrangé
Subject: Re: [Qemu-devel] [PATCH for-4.0 1/7] configure: Add a test for the minimum compiler version
Date: Thu, 6 Dec 2018 09:53:43 +0000
User-agent: Mutt/1.10.1 (2018-07-13)

On Thu, Dec 06, 2018 at 06:34:25AM +0100, Thomas Huth wrote:
> On 2018-12-05 18:30, Philippe Mathieu-Daudé wrote:
> > On 12/3/18 3:05 PM, Thomas Huth wrote:
> >> So far we only had implicit requirements for the minimum compiler version,
> >> e.g. we require at least GCC 4.1 for the support of atomics. However,
> >> such old compiler versions are not tested anymore by the developers, so
> >> they are not really supported anymore. Since we recently declared 
> >> explicitly
> >> what platforms we intend to support, we can also get more explicit on the
> >> compiler version now. The supported distributions use the following version
> >> of GCC:
> >>
> >>       RHEL-7: 4.8.5
> >>       Debian (Stretch): 6.3.0
> >>       Debian (Jessie): 4.8.4
> >>       OpenBSD (ports): 4.9.4
> >>       FreeBSD (ports): 8.2.0
> >>       OpenSUSE Leap 15: 7.3.1
> >>       Ubuntu (Xenial): 5.3.1
> >>       macOS (Homebrew): 8.2.0
> > 
> > I'd like to track this in a machine parsable format, but sure where it
> > better fits however, I'd prefer the git repo, and having the wiki
> > pointing to the git repo.
> 
> I don't think that it makes sense to put fixed version numbers into the
> git or wiki - the information will expire soon, and it is additional
> maintenance to keep them up to date. We already got the generic
> description here:
> 
> https://qemu.weilnetz.de/doc/qemu-doc.html#Supported-build-platforms
> 
> So you just have to follow these instructions to get to the supported
> versions.

Agreed, I don't really see a benefit in tracking the per-distro versions
in QEMU - they're only useful for informing us abuot what min version
to pick, which then goes into configure.

If we absolutely wanted to, we could use a standard variable name in
configure to make it easy to grep for min versions.

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 :|



reply via email to

[Prev in Thread] Current Thread [Next in Thread]