From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Boostrap tar cannot exec xz
Date: Fri, 30 Sep 2016 22:08:17 +0200
Message-ID: <87eg41kv66.fsf@gnu.org>
References: <7tzimpmyss.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33840)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bq46c-0000Ok-H6
	for guix-devel@gnu.org; Fri, 30 Sep 2016 16:08:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1bq46X-0002Xh-Np
	for guix-devel@gnu.org; Fri, 30 Sep 2016 16:08:25 -0400
In-Reply-To: <7tzimpmyss.fsf@gmail.com> ("Carlos =?utf-8?Q?S=C3=A1nchez?= de
	La Lama"'s message of "Fri, 30 Sep 2016 13:06:59 +0200")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Carlos =?utf-8?Q?S=C3=A1nchez?= de La Lama <csanchezdll@gmail.com>
Cc: guix-devel@gnu.org

Hi!

csanchezdll@gmail.com (Carlos S=C3=A1nchez de La Lama) skribis:

> still trying too bootstrap linux-powerpc.

This is exciting, BTW!

> I find the boostrap binary "tar" fails to execute xz (which is un turn
> required to build make on continue the bootstrap process), because it
> can not find bash.
>
> The problem was introduced in your commit
>
> 74d637397b44a90d2dbc2ac100b38591dd4f81eb
>
> which upgraded tar to 1.29. That commit also added the substitution of
> "/bin/sh" to "<bash-store-path>/bin/sh" in src/system.c when compiling
> tar, which is fine in general, but gets broken when %static-binaries
> does a remove-store-reference for all the static binaries.
>
> Is that substitution really needed?

That substitution is needed, because otherwise =E2=80=98tar=E2=80=99 fails =
to spawn
external programs when in a build environment (the chroot lacks
/bin/sh), which causes its own test suite to fail.

I understand that this is not OK for the binaries produced by
make-bootstrap.scm.  However, /bin/sh is not OK either, AFAICS.

In =E2=80=98raw-build=E2=80=99 in bootstrap.scm, we run:

  xz -dc thing.tar.xz | tar xv

to work around this problem.  Isn=E2=80=99t it enough?

Thanks,
Ludo=E2=80=99.