On Wed, 28 Sep 2005 11:32:21 -0400 Venkat Manakkal <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 09/27/2005 01:21 PM, Rumen Yotov wrote: > | On Tue, 27 Sep 2005 13:48:59 +0200 > | kang <[EMAIL PROTECTED]> wrote: > | > | > |>Rumen Yotov wrote: > |> > |> > |>>Hi, > |>>In preparation for my new (third) partition, which will use Xen > |>>virtual machine tried compiling it (just Xen-3 not Xen-sources) on > a |>>RSBAC system. > |>>It failed initially, but went w/o errors when i used "nopienossp" > |>>GCC-3.3.6 profile (haven't tried with GCC-3.4.4-r1) but will later. > |>>This is for your info only, don't think of filing a Bug. > |>>Thanks. Rumen > |>> > |>> > |> > |>Do you mean that you are using a rsbac kernel to compile xen on or > |>that you use a rsbac patched kernel with xen patch and that you try > to |>compile it ? > | > | Hi, > | Yes, compiled Xen on RSBAC system with a hardened compiler etc. > | Think the important part here is the use of hardened > compiler/linker. | Still haven't tied to compile a Xen-patched kernel > on RSBAC, though my | initial intention was to use Xen on a separate > partition, but if | successful could use both kernels (RSBAC & Xen) > on a single partition. | Of course only Xen-0-kernel (superviser > kernel), which can later start | other/userland kernels - Xen-U > kernel. | Thanks.Rumen > > You need to run gcc-config -l and then set the gcc-config to a > non-hardened toolchain - this seems the preferred way of disabling the > hardened toolchain for a given package that seems to not like it. Then > Xen will compile and run. The rest of your system can use the hardened > toolchain. This was my experience with Xen and the same goes for the > common-lisp compiler sbcl. > > Cheers, > > - ---Venkat. > ..SKIP... Hi, Thanks, already done just that.Only wanted to post this as info here. Rumen
pgp6ndpLyrUmI.pgp
Description: PGP signature
