Michael Crute wrote: > I am building a server (AMD Opteron 64) and as a matter of policy I > always run the hardened profile on my servers. Now this is my first > time doing an install on an AMD64 architecture with hardened and so > far it has gone relatively well. The thing that is giving me the most > problems is Grub. When I try to emerge it in the hardened chroot the > config script bombs out with an error 'C compiler cannot create > executables'. One suggested solution was to disable sandbox in > features and try again, no such luck. My next thought was to build a > second chroot with a regular (non-hardened) tarball and build a > package of grub (compiled using the static useflag) then emerge that > in the hardened environment. Does this make sense? Is it likely to > work or should I be doing something else? Any help would be > appreciated. > > Note that simply not using the hardened profile is not an option here. > > -Mike > Hi, Use gcc-config to switch to a vanilla-profile (non-hardened at all). Try to emerge grub then switch back to "hardened". Using non-hardened grub can't become any security thread. PS:could also try latest ~x86 Grub HTH.Rumen
smime.p7s
Description: S/MIME Cryptographic Signature
