On Mon, Aug 22, 2016 at 11:30 AM, Jason L Tibbitts III <ti...@math.uh.edu> wrote:
> >>>>> "DJ" == Dave Johansen <davejohan...@gmail.com> writes: > > DJ> devtoolset is designed to do all of this and is already done, so it > DJ> seems that the only advantage to putting it in EPEL itself would be > DJ> to reduce the number of repos during build time. > > So is devtoolset something I get access to as a CentOS user? How do I > build these packages myself (i.e. in mock)? > The official version used to be behind a paywall, but there were builds by CentOS and CERN. It's now been turned over to a SIG and is all open: https://www.softwarecollections.org/en/scls/?search=devtoolset Building just the compiler part isn't too bad, but building the IDE and other parts of devtoolset takes some working out of the build order that I never worked out because I only cared about the compiler: https://www.redhat.com/archives/sclorg/2016-January/msg00002.html Here's a blog on building SCLs in mock: http://developers.redhat.com/blog/2015/01/07/using-mock-to-build-python27-software-collections-packages-for-rhel6/ For building in COPR, I followed these instructions (but the main magic point is editting each of the supported chroots to have "scl-utils-build <scl_name>-build"): https://www.redhat.com/archives/sclorg/2014-November/msg00015.html
_______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org
