On Mon, Aug 22, 2016 at 11:30 AM, Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote:
>>>>> "DJ" == Dave Johansen <davejohansen@xxxxxxxxx> 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:
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:
Here's a blog on building SCLs in mock:
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"):
_______________________________________________ epel-devel mailing list epel-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
