On Thu, Mar 21, 2013 at 7:19 PM, Dave Johansen <davejohansen at gmail.com> wrote: > > On Wed, Mar 13, 2013 at 3:47 PM, Tru Huynh <tru at centos.org> wrote: > > > > On Sat, Mar 09, 2013 at 02:13:46AM +0000, Karanbir Singh wrote: > > > On 03/08/2013 04:35 AM, Dave Johansen wrote: > > > > I was just on the IRC and because of the recent update to 6.4 through > > > > the CR there was actually a newer version of scl-utils that ended up > > > > being installed. After a little help on the IRC channel I was able to > > > > uninstall the newer scl-utils and install the version from the > > > > developer tools that Tru had built without any problems. So I'm not > > > > sure what the issue was before, but it appears to be working now. > > > > > > > > > > Excellent, however this means there is a problem with the devtools scl > > > not working well with 6.4 ( which is now released and the current > > > CentOS-6 ). If we can verify this, then its worth a note in the ReleaseNotes > > > > > I have just pushed scl-utils-20120927-2.el6.centos and > > scl-utils-build-20120927-2.el6.centos that should fix the issue for CentOS-6.4 > > in my testing area. > > I just noticed that for the 32-bit builds the files are i386 instead > of i686 like the rest of the files. Is that going to cause any > problems? I'm writing up a spec file that depends on devtoolset and then sets CXX to /opt/centos/devtoolset-1.1/root/usr/bin/g++ so that it can use the compiler installed by that package. I was just wonder a few things: 1) Is that the "final" path? Or will it change to match the path in RHEL once this development build of it moves to a permanent location? 2) If the answer to #1 is yes, is there a way to distinguish between RHEL and CentOS in the spec file so it can use the appropriate path for each of them? Thanks, Dave