Am on Arch 64bit, and recently updated gcc and their appropriate toolchain on my laptop
I have been building AOSP Android lately and am facing a load of compile errors (I suspect its the new C++ 0x11 modes switched on somewhere), however, I transferred the source to a 32bit desktop machine that has gcc 4.6.3, and it compiled fine albeit slowly.
At this point I am not looking for suggestions to say go use google-fu to find out if others have that issue with building AOSP or its irrelevant to this thread
Rather, I am looking for a way on how to downgrade the gcc toolchain and what repercussions would that have on the multilibs that also got upgraded as well?
Would it be a matter of going to /var/cache/pacman/pkg and issue pacman -U gcc-4.6.3...tar.gz to downgrade?
Last edited by t0mm13b (2012-04-11 00:51:16)
Right, for reference, the last good known working toolchain prior to 4.7 was as follows in /var/cache/pacman/pkg:
Okie, this is what I did
pacman -U libtool-multilib-2.4.2-4-x86_64.pkg.tar.xz lib32-gcc-libs-4.6.3-1-x86_64.pkg.tar.xz gcc-libs-multilib-4.6.3-1-x86_64.pkg.tar.xz gcc-multilib-4.6.3-1-x86_64.pkg.tar.xz
And to prevent any future breakage, I have added this to my /etc/pacman.conf
IgnorePkg = gcc gcc-libs gcc-libs-multilib gcc-multilib lib32-gcc-libs libtool libtool-multilib
AOSP compiles happily to say and am happy now \o/
Thanks again, will leave this here for reference for anyone else who encounters odd compile issues
Last edited by t0mm13b (2012-04-11 00:54:51)
That will be fun...
The correct way is to build a gcc-4.6 package and compile your program using that.
Well... It takes AOSP GB 2.3.7 android build 8 hours on 32bit crappy desktop machine, 40mins on 64bit laptop
PS: Loved your blog entry about "Windows Service Center", that made me LOL!!!! Nice one!
Last edited by t0mm13b (2012-04-11 01:46:26)