On Mon, Nov 13, 2017 at 9:59 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > On Fri, Oct 21, 2016 at 12:01 AM, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: >>>> I need/want/would like to build new node 6 for EL6, but gcc is too old. >>>> For that reason, I'd like to use devtoolset-4-gcc, but the build fails >>>> (obviously) because the package doesn't exist. >>>> >>>> So, is there a way to make that work somehow? >>>> I am not sure about enabling external repos during build, maybe someone >>>> will be wiser. >>> >>> >>> This has already been discussed several times: >>> https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/KSEYFHCLVPK6DZBDOOPMK46AO65V2SM2/ >>> https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/7HWJYGXFOMEROUYY2TQKZLKC2MSAAA7R/ >>> https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/YQLNZYT5ATELGMHNGET7QCOG3S3UIYT5/ >>> >>> There are some potential roadblocks, but it comes down to someone writing up >>> an official proposal and going through the full approval process. >> >> So one of the major blockers for me for WRT to using DTS in builds it >> that it is currently x86_64 only but with the next release, (DTS 6.0) >> it will support all the RHEL architectures [1] which certainly make it >> easier to support across platforms. We obviously don't want to deal >> with it prior to GA and I have no idea when the intended GA is it's >> certainly worth discussing further now as to what are the >> requirements, advantages, potential issues etc. > > I think this is now worth revisiting, at least for EL7, now DTS is out > and supports key architectures. Thoughts? > > https://developers.redhat.com/blog/2017/10/25/announcing-release-software-collections-developer-toolset-new-compilers/ Smooge: can this be added to the agenda for the next meeting? I'm happy to do the work to enable it, just want to make sure it's wanted before I start. Peter _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
