[blog] 01/02: 133: move stuff from week 134 into the right place

[Ximin Luo]

This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository blog.

commit 2dcf9683e6074d44767af0e9a5869e14b787eb14
Author: Ximin Luo <infinity0 at debian.org>
Date:   Mon Nov 20 16:51:02 2017 +0100

    133: move stuff from week 134 into the right place
---
 drafts/133.mdwn | 30 ++++++------------------------
 drafts/134.mdwn | 29 +++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+), 24 deletions(-)

diff --git a/drafts/133.mdwn b/drafts/133.mdwn
index 20ceb20..744b873 100644
--- a/drafts/133.mdwn
+++ b/drafts/133.mdwn
@@ -18,7 +18,6 @@ We plan to hold [an assembly at
 - hope to see you there!
 
 
-
 LEDE CI tests
 -------------
 
@@ -33,7 +32,10 @@ achieved.
 Bootstrapping and Diverse Double Compilation
 --------------------------------------------
 
-As a follow-up of a [discussion on bootstrapping compilers we had on the Berlin summit](https://pad.riseup.net/p/reproduciblebuildsIII-crossdistro), Bernhard and Ximin worked on a Proof of Concept for Diverse Double Compilation of tinycc (aka tcc).
+As a follow-up of a [discussion on bootstrapping compilers we had on the Berlin
+summit](https://pad.riseup.net/p/reproduciblebuildsIII-crossdistro), Bernhard
+and Ximin worked on a Proof of Concept for Diverse Double Compilation of tinycc
+(aka tcc).
 
 Ximin Luo did a successful [diverse-double compilation of
 tinycc](https://github.com/bmwiedemann/ddcpoc/) git HEAD using gcc-7.2.0,
@@ -41,27 +43,6 @@ clang-4.0.1, icc-18.0.0 and pgcc-17.10-0 (pgcc needs to triple-compile it).
 More variations are planned for the future, with the eventual aim to reproduce
 the same binaries cross-distro, and extend it to test GCC itself.
 
-Work on bootstrapping also made progress in (MesCC)[https://gitlab.com/janneke/mes] from Jan Nieuwenhuizen.
-MesCC now compiles a less heavily patched TinyCC into a mes-tcc that in turn passes 41/69 of mescc's C tests.
-
-
-BUILD_PATH_PREFIX_MAP, `__FILE__` and Qt
-----------------------------------------
-
-A patch to support the [BUILD_PATH_PREFIX_MAP](https://reproducible-builds.org/specs/build-path-prefix-map/)
-environment variable to avoid embedding build-time paths into generated files
-has been [proposed to GCC](https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00513.html).
-This patch also affects the `__FILE__` environment variable, mapping it in the
-same way that debug-prefix-map works for debug symbols. The patch as it was sent
-was rejected with some concerns, and work is under way to adapt the patch to
-address those concerns.
-
-The behaviour was already backported to the patched GCC that is used for the
-unstable tests on https://tests.reproducible-builds.org . This showed that the
-new behaviour [causes problems with Qt applications using QFINDTESTDATA in
-build-time tests](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901),
-since they rely on `__FILE__` being a valid (relative) file system path at build
-time.
 
 Packages reviewed and fixed, and bugs filed
 -------------------------------------------
@@ -209,4 +190,5 @@ Misc.
 -----
 
 This week's edition was written by Ximin Luo, Bernhard M. Wiedemann, Chris Lamb
-and Holger Levsen & reviewed by a bunch of Reproducible Builds folks on IRC & the mailing lists.
+and Holger Levsen & reviewed by a bunch of Reproducible Builds folks on IRC &
+the mailing lists.
diff --git a/drafts/134.mdwn b/drafts/134.mdwn
index 14f6359..8cfca3c 100644
--- a/drafts/134.mdwn
+++ b/drafts/134.mdwn
@@ -19,6 +19,7 @@ Reproducible work in other projects
 
 * The Google Container Tools team [announced the release of container-diff](https://opensource.googleblog.com/2017/11/container-diff-for-comparing-container-images.html), a new project to help uncover differences between container images.
 
+
 Upcoming events
 ---------------
 
@@ -31,6 +32,34 @@ Past events
 On November 17th Chris Lamb presented at the [Open Compliance Summit](http://events.linuxfoundation.org/events/open-compliance-summit/) in Yokohama, Japan on how reproducible builds can ensure the long-term sustainability of technology infrastructure.
 
 
+Bootstrapping and Diverse Double Compilation
+--------------------------------------------
+
+Work on bootstrapping also made progress in
+(MesCC)[https://gitlab.com/janneke/mes] from Jan Nieuwenhuizen. MesCC now
+compiles a less heavily patched TinyCC into a mes-tcc that in turn passes 41/69
+of mescc's C tests.
+
+
+BUILD_PATH_PREFIX_MAP, `__FILE__` and Qt
+----------------------------------------
+
+A patch to support the [BUILD_PATH_PREFIX_MAP](https://reproducible-builds.org/specs/build-path-prefix-map/)
+environment variable to avoid embedding build-time paths into generated files
+has been [proposed to GCC](https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00513.html).
+This patch also affects the `__FILE__` environment variable, mapping it in the
+same way that debug-prefix-map works for debug symbols. The patch as it was sent
+was rejected with some concerns, and work is under way to adapt the patch to
+address those concerns.
+
+The behaviour was already backported to the patched GCC that is used for the
+unstable tests on https://tests.reproducible-builds.org . This showed that the
+new behaviour [causes problems with Qt applications using QFINDTESTDATA in
+build-time tests](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901),
+since they rely on `__FILE__` being a valid (relative) file system path at build
+time.
+
+
 Packages reviewed and fixed, and bugs filed
 -------------------------------------------
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/blog.git