Hello! Yes, we're dropping support for such an old GCC, mostly because we don't have enough resources (time) to manage those old systems for testing. Other problems are with lack of support of some C11 features. I should also say that the upcoming multithreaded versions will also need a reasonably new compiler to support thread local storage and maybe C11 atomics also.
Sorry for that. We try our best, yet keeping backwards compatibility with old systems is quite a lot of work for us. BTW you can still use your old GCC to build a newer GCC or Clang locally and then build BIRD using that compiler, however it is in most cases an insane overkill. Maria On July 2, 2020 8:04:08 AM GMT+02:00, Tim Meusel <b...@bastelfreak.de> wrote: >Hi Robert, > >thanks for the answer. I already assumed such an issue :( >I'm aware of the EOL in November, but I'm afraid I still need to roll >it out up to that date. > >Thanks for your quick answer. I will go with Bird 1 in that case. > >Regards, Tim > >On 01.07.20 22:05, Robert Scheck wrote: >> On Wed, 01 Jul 2020, Tim Meusel wrote: >>> I'm happily using Bird 2 on multiple CentOS 7 nodes. Sadly I now >need to >>> rollout BGP to some CentOS 6 boxes :sadface:. I noticed that >>> ftp://bird.network.cz/pub/bird/centos/ only contains CentOS 7 >packages, >>> and EPEL 6 only has Bird 1.6.8. However I wanted to ask if Bird 2 >would >>> work on CentOS 6? Would Bird itself compile but dependencies are >>> outdated/missing? >> >> since BIRD 2.0.5, a C compiler newer than contained in CentOS 6 is >needed; >> I had to drop BIRD 2 from EPEL 6 due to this. See also the old thread >here: >> >> - >http://trubka.network.cz/pipermail/bird-users/2019-August/013634.html >> - >http://trubka.network.cz/pipermail/bird-users/2019-August/013631.html >> >> But given CentOS 6 reaches end of lifetime in November (!), please >migrate >> these boxes to CentOS 8 or at least 7. There, BIRD 2 is even in EPEL >:) >> >> >> Regards, >> Robert >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
