On 02/27/2014 12:06 AM, titan wrote: > ok > build.log: http://pastebin.com/BvQ5au2h > root.log: http://pastebin.com/UF5kPPuj When building SCL packages, you need to add 2 things to the build root directly ... scl-utils-build and <scl_name>-build package Your root log seems to have scl-utils-build, but not python27-build. So the process is this: 1. Build the latest scl-utils package (looks like you have done that). 2. Build latest scl metadata package, in this case python27-1-10.el6.src.rpm package (that is not in your build root). This produces python27-1-10.el6.x86_64.rpm and python27-build-1-10.el6.x86_64.rpm 3. Add in these two packages to your mock root: scl-utils-build and <scl_name>-build (in this case python27-build) See this whole mailing list thread for details: https://lists.fedorahosted.org/pipermail/softwarecollections/2012-November/000018.html So, You need to have a separate mock config file for each SCL (ie, one for python27 and another one for python33 or mysql55, etc) ... and you need to modify the line: config_opts['chroot_setup_cmd'] = so that it contains the build group and add to it scl-utils-build python27-build as explained in the above link (in that case perl514 is the scl name and they have this): config_opts['chroot_setup_cmd'] = 'install @build scl-utils-build perl514-build' ================= The real question is ... why are you trying to build SCLs, when you can just do: yum install centos-release-SCL then use the CentOS compiled version of SCLs (in this case ... yum install python27) See our release announce for more info: http://lists.centos.org/pipermail/centos-announce/2014-February/020164.html
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
