On 11/10/2018 16:31, Miklos Vajna wrote:
* Completed Action Items:
    + setup new CentOS7 baseline VM (Cloph)
      [ done for the 64bit builds, for 32bit we stick to the CentOS6 ]
      [ which means GCC requirements could be bumped to GCC 7 on master
        now; Stephan will take care ]
as discussed on FreeNode #libreoffice-dev afterwards:
Oct 11 16:58:21 <sberg>   cloph, re GCC version, e.g. today's 
<https://ci.libreoffice.org/job/lo_tb_master_linux/30783/> appears to still be done with GCC 4.8?  (seeing "export 
GCC_VERSION=408" in <https://ci.libreoffice.org/job/lo_tb_master_linux/30783/console>)
Oct 11 16:59:38 <cloph>   that's what I meant: the jenkins buildslaves' still need to be updated.
Oct 11 17:01:30 <sberg>   cloph, ah, then I misunderstood you in the call; please let me know once 
they're updated :)
Oct 11 17:05:30 <cloph>   oh, and I didn't check whether gperf 3.0.4 is proper (seems it is not, 
still std=gnu++14)
(the last comment is re 
<https://lists.freedesktop.org/archives/libreoffice/2018-September/080945.html> 
"Re: Compiler baselines": "Also saw that on CentOS 6 
gperf-3.0.3-9.1.el6.x86_64 is too old, still
emitting register keywords in C++ mode, so that our configure.ac falls
back to using -std=gnu++14 instead of -std=gnu++17.  So the relevant
machines would also need a newer gperf (e.g., built from
gperf-3.1.tar.gz sources and passed into the LO build via a GPERF=...
line in autogen.input).")
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.