C11 support now required for v3.1.x (3.2.0)
a.cudbardb at freeradius.org
Thu Jun 2 03:06:33 CEST 2016
_Generic support is now required to build FreeRADIUS v3.1.x which will become 3.2.0.
This means the minimum GCC version is now 4.9.0 (April 22, 2014) and clang version 3.0 (Nov 30, 2011).
[xxx ~]$ uname -a
Linux xxx 3.10.0-229.20.1.el7.x86_64 #1 SMP Thu Sep 24 12:23:56 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC)
So RHEL7 users wanting to use the latest version of FreeRADIUS are going to experience issues, because providing a compiler that supports C11 *NEARLY FIVE YEARS* after it was released, is apparently not a priority for RHT.
You can't even build the latest versions of Clang on RHEL7 to get C11 support, because it requires C++11 support!
I know, I know, GCC 4.9.3 hasn't been blessed by the requisite number of QA engineers, but I wonder, maybe, just, maybe, just this once, RHT could release software that hasn't been through the five year circle jerk (validation) process?
*sigh* So I'm off to build my unsupported tool chain, to build an unsupported version of FreeRADIUS, against an unsupported version of OpenSSL*, and an unsupported version of libldap**.
Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
* Needed for RSA acceleration (because who uses RSA‽).
** RHT builds theirs against NSS which is ABI incompatible with OpenSSL and causes crashes when linked against software that uses OpenSSL (almost everything ever‽).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Freeradius-Devel