From: ilove zfs <ilovezfs@icloud.com>
To: Dan Kegel <dank@kegel.com>
Cc: 30011@debbugs.gnu.org
Subject: bug#30011: BSD sed incompatibility as of guile 2.2.3
Date: Sun, 07 Jan 2018 21:05:34 +0000 (GMT) [thread overview]
Message-ID: <7ad224d3-6534-4e6f-ba92-673f4b7d82f2@me.com> (raw)
In-Reply-To: <70f7ca0c-fc4d-4686-abc2-261cf1f8f908@me.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
In case it helps, here are full build logs:
https://github.com/Homebrew/homebrew-core/pull/22542
https://jenkins.brew.sh/job/Homebrew%20Core%20Pull%20Requests/16097/version=high_sierra/console
https://jenkins.brew.sh/job/Homebrew%20Core%20Pull%20Requests/16097/version=sierra/console
https://jenkins.brew.sh/job/Homebrew%20Core%20Pull%20Requests/16097/version=el_capitan/console
I can reproduce it locally, outside of Homebrew, with the release tarball, and the problem occurs during `make install` not `make`.
On Jan 07, 2018, at 12:12 PM, ilove zfs <ilovezfs@icloud.com> wrote:
The build is indeed using https://ftp.gnu.org/gnu/guile/guile-2.2.3.tar.xz
> I don't run into that in my build of 2.2.3 on macosx.
You may have gnu-sed installed then.
On Jan 07, 2018, at 11:41 AM, Dan Kegel <dank@kegel.com> wrote:
Builds from release tarball might not run into this,
as the tarball already includes the file that rule creates;
at any rate, I don't run into that in my build of 2.2.3 on macosx.
[-- Attachment #2.1: Type: text/html, Size: 2307 bytes --]
next prev parent reply other threads:[~2018-01-07 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 10:35 bug#30011: BSD sed incompatibility as of guile 2.2.3 ilove zfs
2018-01-07 19:41 ` Dan Kegel
2018-01-07 20:12 ` ilove zfs
2018-01-07 21:05 ` ilove zfs [this message]
2018-02-16 14:31 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ad224d3-6534-4e6f-ba92-673f4b7d82f2@me.com \
--to=ilovezfs@icloud.com \
--cc=30011@debbugs.gnu.org \
--cc=dank@kegel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).