All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Doug Goldstein <cardoe@cardoe.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] automation: add SLES 11 SP4 dockerfile
Date: Wed, 18 Jul 2018 11:44:40 +0200	[thread overview]
Message-ID: <20180718094404.GA8304@aepfle.de> (raw)
In-Reply-To: <20180717200305.4067-1-wei.liu2@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 753 bytes --]

On Tue, Jul 17, Wei Liu wrote:

> No OVMF because it requires gcc 4.4 or later.

Fine.

> No seabios because it requires anonymous union initialisation

It is required to build Xen like that (with a custom compiler from gcc48.rpm):

test -x "$(type -p gcc)" && CC=$_
test -x "$(type -p gcc-4.8)" && CC=$_
make \
        CC=$CC \
        HOSTCC=$CC \
        xen

make \
        CC=$CC \
        GCC=$CC \
        HOSTCC=$CC \
        HOST_CC=$CC \
        BUILD_CC=$CC \
        tools stubdom

> No QEMU upstrea because sed doesn't support -E.

libvirt+QEMU upstream does not support SLE11 anymore due to the
requirement for a newer glib2. In case Xen wants to stick with qemu-2.12
for a while, SLE11 could still be tested for fun and education.


Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2018-07-18  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 20:03 [PATCH] automation: add SLES 11 SP4 dockerfile Wei Liu
2018-07-17 20:06 ` Wei Liu
2018-07-17 20:42 ` Doug Goldstein
2018-07-18  7:25 ` Jan Beulich
2018-07-18  8:04   ` Wei Liu
2018-07-18  9:44 ` Olaf Hering [this message]
2018-07-18  9:51   ` Wei Liu

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=20180718094404.GA8304@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=cardoe@cardoe.com \
    --cc=jbeulich@suse.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.