From: [EMAIL PROTECTED] Date: Mon, 23 May 2005 13:24:18 -0700 > The other alternative is to "touch /etc/disable_64_gcc
Sure, but in the mail you are specifically replying to I stated: > > Also, /etc/disable_64_gcc is a workaround and should not be there > > by default as it is now, especially on your build machines. So I > > highly recommend that the build machine environment setup I > > described above is implemented. > > > > I'm going to be making GCC do this in the vanilla gcc sources by > > default, I've already convinced the other Sparc backend > > maintainers that it is the absolute right thing to do. And it > > won't be checking for the /etc/disable_64_gcc workaround file. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
