So no gardening was done. On the plus side that left plently of time for catching up on housework stuff and writing a new Gentoo application. rc-depend is a C program that works out dependencies and ordering of all your init scripts. This was written because our bash logic, although now seemingly 100% accurate, was incredibly slow taking around 2-3 seconds on my 2Ghz laptop to work it out. rc-depend works it out in 0.
OK, so after much nashing of teeth over Python not emerging, I bit the bullet and wiped my disk :jawdrop:
One reboot and wanging my new stage3 onto my sparc I discovered a few missing files- heh. Most of them were the fault of baselayout not installing system FreeBSD files (bad me) and one was a gcc-config bug where mv/cp is linked against libgcc_s.so as such can’t copy libgcc_s.so from the specific gcc lib dir to /lib.
is what it took to emerge-e system. And no errors too :D OK, I had put python into package.provided as it just refuses to re-emerge for no good reason. If anyone has any insight into what is causing that then please let me know!
I rebooted and get kernel panics soon after loading rc and I thought eeek! wtf! :sick: So after chrooting of a livecd and swapping FreeBSD rc other with Gentoo baselayout I rebooted again ….
Well, I hope it is :P
My SPARC has now got to the stage where all base system packages + a few extras I need (openvpn, dhcp, keychain, etc) have emerged successfully :) I’ve even managed to compile and install a custom kernel. The one thing I’ve not done yet is rebooted to check that the new kernel and boot loader actually work.
So all I have todo is emerge-e world twice to make 100% sure everything is peachy, rebuild the kernel again and reboot.
Builtin defines from gcc are useful- they give you some information about your arch. __i386__, __amd64__ and so on.
sparc is a little wierd- here’s a quick list
__sparc__ __sparc64__ __sparc_v9__ Now, FreeBSD only supports Sparc64 and has lots of checks using #ifdef __sparc64__. At first glance, this looks OK and there appears to be nothing wrong with it. However, gcc likes to define __sparc64__ as a CPU type (as I understand it) and is no guarantee of 64-bit code.
Roy's Blog