Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Remove SH_USE_BSD_ECHO autoconf test.
- X-seq: zsh-workers 40237
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [PATCH] Remove SH_USE_BSD_ECHO autoconf test.
- Date: Mon, 26 Dec 2016 02:58:08 +0000
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= mesmtp; bh=bkC2roo4JSlFc3mIzHYdiLE4N/g=; b=qoBS83BZJsFboAvl1e/rK gYvaZWnijEdBzHg9xYqkhJDt0as9knB2RQEQhD3PenJdT2/5kpJGJXu03CrfQg0o 4p8u9l3Lj5g9ccA5P9JoyYVVFjs2ZNcB+LivndDqmOee2+At8IZOag4yY7QNIzjM bmu1LPZ7KPz+zzF30IQSqc=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=bkC2roo4JSlFc3mIzHYdiLE4N/g=; b=il4njxpb7uS/QnKNzzwk wriCYL+s7Sx7RpFEoHKTcjkCdhDypKBswpxdED0+/n/aa/sWjzRzjHSAhXMvSnUi vokPpDhihvZRgtiMMWwsJf5vOGUhqKTmtXZqpM3Tbrgxm5dszDRx8H30ZVr2uU41 ZMICUGJpEe58Yq1hA1Y3p4M=
- In-reply-to: <161225100619.ZM26202@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <1482601418-17984-1-git-send-email-danielsh@fujitsu.shahaf.local2> <161224135231.ZM29868@torch.brasslantern.com> <20161225023331.GA10957@fujitsu.shahaf.local2> <161225100619.ZM26202@torch.brasslantern.com>
Bart Schaefer wrote on Sun, Dec 25, 2016 at 10:06:19 -0800:
> Further the whole point of "configure" is to produce results that might
> vary based on the buid environment. Reproducibility should only apply
> downstream of configuration, if it's to have any value at all.
Sure; reproducibility means that given the same inputs, the (bitwise
identical) same output is produced. Flags to configure are obviously
part of the input. What was being tested here is that the behaviour of
«/bin/sh -c 'echo "\n"'» is _not_ part of the input, i.e., that the same
output is produced even for build environments having different
/bin/sh's.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author