://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 wrote:
The build is indeed using
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 wrote:
Builds from release tarball might not run into this,
as the tarball alre
The following commit broke compatibility with BSD/macOS's version of sed:
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=81d2e352663bc5f80734312fec90f250b1fbe2e4
The error is "sed: -i may not be used with stdin" as described in
https://stackoverflow.com/questions/21242932/sed-i-may
On macOS 10.11 and 10.12 building with Xcode 8, guile 2.1.7 fails to compile with several
errors saying "address argument to atomic operation must be a pointer to _Atomic
type." I can avoid this by setting ac_cv_header_stdatomic_h=no.
Build logs here:
https://gist.github.com/ilovezfs/b18b7e61
Despite the "accept4 flags. No ifdef as accept4 has a gnulib implementation"
building 2.1.7 fails with undeclared identifier errors for SOCK_CLOEXEC and SOCK_NONBLOCK
on macOS. Wrapping the relevant sections in ifdef SOCK_CLOEXEC and ifdef SOCK_NONBLOCK
seems to work around the build failure,
