From: Rajiv Ranganath <rajiv.ranganath@atihita.com>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org
Subject: [stage1-xen (RFC) PATCH 02/10] build/fedora: Add `buildroot-README.md`
Date: Mon, 21 Aug 2017 12:47:43 +0530 [thread overview]
Message-ID: <20170821071743.65172.96274.stgit@rajivs-macbook-pro.local> (raw)
In-Reply-To: <20170821071721.65172.78369.stgit@rajivs-macbook-pro.local>
From: Rajiv M Ranganath <rajiv.ranganath@atihita.com>
---
build/fedora/buildroot-README.md | 50 ++++++++++++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
create mode 100644 build/fedora/buildroot-README.md
diff --git a/build/fedora/buildroot-README.md b/build/fedora/buildroot-README.md
new file mode 100644
index 0000000..0efb150
--- /dev/null
+++ b/build/fedora/buildroot-README.md
@@ -0,0 +1,50 @@
+## stage1-xen Fedora Buildroot
+
+stage1-xen build artifacts for Fedora is built in two phases. In the first phase
+a docker container is prepared with all the build dependencies. We refer to it
+as `stage1-xen-fedora-buildroot`. In the next phase we execute the `run` script
+that uses `stage1-xen-fedora-buildroot` and to produce the build artifacts.
+
+### Building `stage1-xen-fedora-buildroot`
+
+`stage1-xen-fedora-buildroot` has a external dependency
+on [`binutils`](https://github.com/lambda-linux-fedora/binutils) package that is
+compiled with `i386pe` support. You can download the pre-built RPMs
+from [here](https://drive.google.com/open?id=0B_tTbuxmuRzIR05wQ3E1eWVyaGs).
+Please download `binutils-2.26.1-1.1.fc25.tar`.
+
+To build docker image
+
+```
+cd stage1-xen/build/fedora
+
+docker build -f buildroot-Dockerfile -t stage1-xen-fedora-buildroot .
+```
+
+### Running `stage1-xen-fedora-buildroot`
+
+```
+cd stage1-xen
+
+docker run --rm \
+ -v `pwd`:/root/gopath/src/github.com/rkt/stage1-xen \
+ -v /tmp:/tmp \
+ -t -i stage1-xen-fedora-buildroot \
+ /sbin/my_init -- /root/bin/run
+```
+
+The generated build artifacts are in `/tmp` directory.
+
+To debug build issues -
+
+```
+cd stage1-xen
+
+docker run --rm \
+ -v `pwd`:/root/gopath/src/github.com/rkt/stage1-xen \
+ -v /tmp:/tmp \
+ -t -i stage1-xen-fedora-buildroot \
+ /sbin/my_init -- /bin/bash
+```
+
+Also see section on `ipdb` in `buildroot-Dockerfile`.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-21 7:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 7:17 [stage1-xen (RFC) PATCH 00/10] Add Fedora support Rajiv Ranganath
2017-08-21 7:17 ` [stage1-xen (RFC) PATCH 01/10] .gitignore: Add Rajiv Ranganath
2017-08-21 7:17 ` Rajiv Ranganath [this message]
2017-08-21 8:30 ` [stage1-xen (RFC) PATCH 02/10] build/fedora: Add `buildroot-README.md` M A Young
2017-08-24 0:22 ` Stefano Stabellini
2017-08-21 7:17 ` [stage1-xen (RFC) PATCH 03/10] build/fedora: Add `buildroot-Dockerfile` Rajiv Ranganath
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 04/10] build/fedora: Add `run` Rajiv Ranganath
2017-08-24 0:21 ` Stefano Stabellini
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 05/10] build/fedora: Add `source_path.sh` Rajiv Ranganath
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 06/10] build/fedora: Add `xen-unstable-runit/*` scripts Rajiv Ranganath
2017-08-24 0:51 ` Stefano Stabellini
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 07/10] .circleci/config.yml: Add Rajiv Ranganath
2017-08-24 0:24 ` Stefano Stabellini
2017-08-24 10:39 ` Rajiv Ranganath
2017-08-25 0:56 ` Stefano Stabellini
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 08/10] README.md: Add CircleCI badge Rajiv Ranganath
2017-08-24 0:24 ` Stefano Stabellini
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 09/10] build/fedora: Add `RUNNING_STAGE1_XEN.md` Rajiv Ranganath
2017-08-24 0:37 ` Stefano Stabellini
2017-08-21 7:18 ` [stage1-xen (RFC) PATCH 10/10] BUILDING.md: Add Fedora instructions Rajiv Ranganath
2017-08-24 0:42 ` Stefano Stabellini
2017-08-24 0:01 ` [stage1-xen (RFC) PATCH 00/10] Add Fedora support Stefano Stabellini
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=20170821071743.65172.96274.stgit@rajivs-macbook-pro.local \
--to=rajiv.ranganath@atihita.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).