From: "Kevin F. Quinn (Gentoo)" <kevquinn@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Problems compiling xen - please help...
Date: Thu, 2 Feb 2006 18:34:02 +0100 [thread overview]
Message-ID: <20060202183402.5be7ea34@c1358217.kevquinn.com> (raw)
In-Reply-To: <43E21F59.9070709@wildgooses.com>
[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]
On Thu, 02 Feb 2006 15:03:53 +0000
Ed W <lists@wildgooses.com> wrote:
> I am trying to get Xen running under a hardened kernel. The machine
> is currently booted with "selinux=1 enforcing=0". I am having
> trouble compiling:
File a bug. These unresolved symbols indicate those files have been
compiled with the stack protector on, as can be seen from the
compilation lines. However while the ebuild does do the 'filter-flags
-fPIE -fstack-protector' the build is ignoring CFLAGS for some of its
compilations.
An alternative for now, is to switch to the -hardenednopiessp variant
of your compiler and build it with that.
> gcc -DDEBUG -D_ACPI_ -DTEXTADDR=0x000D0000 -I. -I../../../tools/libxc
> -Wall -fno-builtin -O2 -msoft-float -m32 -march=i686 -D__ASSEMBLY__
> -DDEBUG -D_ACPI_ -DTEXTADDR=0x000D0000 -c trap.S
> gcc -DDEBUG -D_ACPI_ -DTEXTADDR=0x000D0000 -I. -I../../../tools/libxc
> -Wall -fno-builtin -O2 -msoft-float -m32 -march=i686 -c vm86.c
> gcc -DDEBUG -D_ACPI_ -DTEXTADDR=0x000D0000 -I. -I../../../tools/libxc
> -Wall -fno-builtin -O2 -msoft-float -m32 -march=i686 -c setup.c
> gcc -DDEBUG -D_ACPI_ -DTEXTADDR=0x000D0000 -I. -I../../../tools/libxc
> -Wall -fno-builtin -O2 -msoft-float -m32 -march=i686 -c util.c
> cpp -P -DDEBUG -D_ACPI_ -DTEXTADDR=0x000D0000 vmxassist.ld >
> vmxassist.tmp ld -o vmxassist -m elf_i386 -nostdlib --fatal-warnings
> -N -T vmxassist.tmp head.o trap.o vm86.o setup.o util.o
> vm86.o: In function `address':
> vm86.c:(.text+0x19): undefined reference to `__guard'
> vm86.c:(.text+0x56): undefined reference to `__stack_smash_handler'
> vm86.o: In function `trace':
> vm86.c:(.text+0xe9): undefined reference to `__guard'
> vm86.c:(.text+0x141): undefined reference to `__guard'
> vm86.c:(.text+0x15d): undefined reference to `__stack_smash_handler'
> vm86.o: In function `getreg':
> vm86.c:(.text+0x278): undefined reference to `__guard'
> vm86.o: In function `.L23':
> ...etc...
>
>
> I have tried various combinations of compiler using gcc-config.
> Neither gcc-3.4.4 or gcc-3.3.6 seem to do any better, hardened or not
>
> I suspect that this could be a problem with the compiler still using
> some hardend profile despite me asking for a non-hardened gcc? Can
> anyone please help debug this
>
> Ed W
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-02 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 15:03 [gentoo-hardened] Problems compiling xen - please help Ed W
2006-02-02 15:48 ` Ned Ludd
2006-02-02 15:53 ` Ed W
2006-02-02 17:02 ` Ed W
2006-02-04 10:16 ` Peter S. Mazinger
2006-02-02 17:34 ` Kevin F. Quinn (Gentoo) [this message]
2006-02-02 17:52 ` Ed W
2006-02-02 17:59 ` Ed W
2006-02-02 18:18 ` Ned Ludd
2006-02-02 19:35 ` Kevin F. Quinn (Gentoo)
2006-02-02 20:35 ` Ned Ludd
2006-02-02 21:41 ` Kevin F. Quinn (Gentoo)
2006-02-04 10:12 ` Peter S. Mazinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060202183402.5be7ea34@c1358217.kevquinn.com \
--to=kevquinn@gentoo.org \
--cc=gentoo-hardened@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox