On 2018-11-28 17:58, Daniel P. Berrangé wrote: > On Wed, Nov 28, 2018 at 05:50:38PM +0100, Thomas Huth wrote: >> On 2018-11-28 17:05, Daniel P. Berrangé wrote: >>> On Wed, Nov 28, 2018 at 10:58:14AM +0100, Thomas Huth wrote: >>>> Clang 3.4 does not know the "flatten" attribute yet. We've already >>>> introduced the QEMU_FLATTEN macro for this in commit 97ff87c0ed020c2, >>>> so use this macro now here, too, to fix this issue. >>>> >>>> Signed-off-by: Thomas Huth <th...@redhat.com> >>> >>> Although we currently only aim to support CLang and GCC, we don't have >>> any checks for a minimum version of these two tools in configure. >>> >>> So I was wondering if we actually still need to support CLang 3.4 at all >>> in QEMU, given our targetted build platforms. >>> >>> Unfortunately repology.org is failing me in reporting clang versions >>> for most distros, so I don't have an answer yet. I do see that Debian >>> Jessie however ships clang == 3.5 and that's usually the oldest distro >>> if RHEL hasn't got something older. >> >> I'm using RHEL7 and the clang that I get "for free" is 3.4.2 via EPEL. > > Hmm, raises interesting question of whether we should consider 3rd > party repos for purposes of determining our min versions. > > I'd pretty much intended to only care about vendor provided repos, > in which case RHEL7 would be considered to lack clang, for purposes > of deciding min versions. > > EPEL is a bit murky because while it is a 3rd party repo, many users > of RHEL consider to be a defacto standard repo.
Looks like there's also the possibility to get newer versions of Clang on top of RHEL7: https://developers.redhat.com/blog/2018/07/07/yum-install-gcc7-clang/ ... so fine for me if we use another version as the minimum. But if we decide to use 3.4 as minimum version, I'll keep my current compiler to be able to report problems... Thomas
