On 12/25/2015 09:51 PM, Bryce wrote: > eh wot? > I built silo as pure 64bit, but since you can't 'chainload' from 32bit > silo to 64bit silo...
I tried building 64-bit natively but that failed with: gcc -Os -Wall -I. -I../include -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000 -DLARGE_RELOC=0x380000 -fno-stack-protector -c divdi3.S divdi3.S: Assembler messages: divdi3.S:105: Error: detected global register use not covered by .register pseudo-op Then I looked at http://git.kernel.org/cgit/linux/kernel/git/davem /silo.git/tree/Rules.make and saw "CC=gcc -m32" and I assumed silo always has to be 32 bits. I haven't built silo before and I just assumed this has to be correct, especially since silo has always been built on Debian with -m32 and it always loaded a 64-bit sparc64 kernel. If loading a 64-bit kernel from a 32-bit silo is not possible, how did it work in Debian in the sparc port (which uses a 64-bit kernel)? If that's not right, please let me know what's the proper way, and please, please, please get all your silo fixes upstreamed so I can access them easily. > So are your options here a bit twisted by the need to support 32 and > 64bit at the same time? No, I want to create a pure 64-bit sparc64 installation image. Any help and input is *HIGHLY* appreciated! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
