From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally built ones Date: Mon, 22 Jul 2019 10:26:30 +0200 Message-ID: <878ssqsceh.fsf@gnu.org> References: <875znwcoo9.fsf@netris.org> <87ef2j1pgt.fsf@gnu.org> <87ftmy51kk.fsf@netris.org> <87muh6sib4.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:51982) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hpTex-00034C-Cs for bug-guix@gnu.org; Mon, 22 Jul 2019 04:27:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hpTew-0001Qk-A4 for bug-guix@gnu.org; Mon, 22 Jul 2019 04:27:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:51095) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hpTew-0001QV-6M for bug-guix@gnu.org; Mon, 22 Jul 2019 04:27:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87muh6sib4.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 22 Jul 2019 08:18:55 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 36747@debbugs.gnu.org Jan Nieuwenhuizen writes: >> What I need is a way to build the new bootstrap tarballs without using >> the existing 'core-updates' branch. I need a way to build them from a >> branch that's based upon the much older bootstrap binaries that we've >> been using for many years. Preferably, they should be built from >> something close to current 'master'. >> >> Is this feasible? > > Hmm, I'm not sure how much work it would be. If we're lucky then the > recipes from gnu/packages/bootstrap.scm for mescc-tools-static-stripped > and mes-minimal-stripped and their tarballs could be put into and used > on master to build. I'll have a look into this. Yes, this probably works. I have pushed a `wip-binaries' branch, branched-off of current master and added recipes for mescc-tools and mes bootstrap tarballs. I have put the results of --8<---------------cut here---------------start------------->8--- ./pre-inst-env guix build --system=3Di686-linux mes-minimal-stripped-tarball ./pre-inst-env guix build --system=3Di686-linux mescc-tools-static-stripped= -tarball --8<---------------cut here---------------end--------------->8--- here: http://lilypond.org/janneke/guix/20190722/ Once the patches are cleaned-up/we decide how we want it, we can build and inject the resulting binaries into current core-updates. I don't really like it a lot to have built them on a totally new branch but it's the best we can do right now, I think. Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.com