On Tue, 5 Dec 2017, kefu chai wrote: > On Thu, Nov 30, 2017 at 10:38 PM, Sage Weil <sweil@xxxxxxxxxx> wrote: > > On Thu, 30 Nov 2017, Nathan Cutler wrote: > >> I thought we already agreed to drop Trusty in Mimic? > > > > I'm not sure we made any final decision, but I haven't seen anyone > > complain this time around, so I'd say let's do it! > > good news, every one! we are now building ceph using gcc-7 on centos7 > and trusty. > > an example build with gcc-4.8 on trusty: > https://jenkins.ceph.com/job/ceph-dev-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=trusty,DIST=trusty,MACHINE_SIZE=huge/13152//consoleFull > /// we have following warning message: > ----8<---- > CMake Warning at src/CMakeLists.txt:176 (message): > performance regression is expected due to an O(n) implementation of > 'std::list::size()' in libstdc++ older than 5.1.0 > ------>8---- > an example build with gcc-7 on trusty: > see https://jenkins.ceph.com/job/ceph-dev-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=trusty,DIST=trusty,MACHINE_SIZE=huge/13156//consoleFull > /// the warning message is gone. > > a build with gcc-7 on centos-7, > see https://jenkins.ceph.com/job/ceph-dev-build/ARCH=x86_64,AVAILABLE_ARCH=x86_64,AVAILABLE_DIST=centos7,DIST=centos7,MACHINE_SIZE=huge/13155//consoleFull Yay!! > once all trusty testnodes are re-imaged with xenial, i will try to > remove the trusty build support on ceph/ceph-build. BTW, if we want to > use gcc-7 on xenial, which ships GCC 5.3, we can apply the same fix on > it also. I think we need to keep the trusty build support there for luminous and jewel builds, right? > the only issue is http://tracker.ceph.com/issues/22301. its fix is > pending on review. > > -- > Regards > Kefu Chai > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
