Alternatively, rather than applying that ugly unreviewed patch, we could
probably just pass ac_cv_func_clock_gettime=no to configure to avoid the
new system calls until upstream catches up with the deviations in the Mac
OS X implementation.
Jack
On Mon, Aug 15, 2016 at 1:22 PM,
> On Aug 15, 2016, at 10:22, Jack Howarth wrote:
>
> The build issue for guile20 (and I assume also guile18) on 10.12 is described
> in...
>
> http://lists.gnu.org/archive/html/bug-guile/2016-06/msg00252.html
>
The build issue for guile20 (and I assume also guile18) on 10.12 is
described in...
http://lists.gnu.org/archive/html/bug-guile/2016-06/msg00252.html
and a hack to work around it proposed at...
https://gist.github.com/rahulg/baa500e84136f0965e9ade2fb36b90ba
Jack
On August 15, 2016 at 12:19:26, Alexander Hansen
(alexanderk.han...@gmail.com(mailto:alexanderk.han...@gmail.com)) wrote:
> >
> > On Aug 15, 2016, at 05:10, Kevin Gardner wrote:
> >
> > Hi all:
> > Running into a fatal compilation error for guile20 under the bleeding edge
> > MacOS 10.12
> On Aug 15, 2016, at 05:10, Kevin Gardner wrote:
>
>
> Hi all:
>Running into a fatal compilation error for guile20 under the bleeding edge
> MacOS 10.12 / XCode 8 / fink sierra-alpha-bravo combination. Info attached
> below, glad to provide more as needed
Hi all:
Running into a fatal compilation error for guile20 under the bleeding edge
MacOS 10.12 / XCode 8 / fink sierra-alpha-bravo combination. Info attached
below, glad to provide more as needed —
Thanks,
Kevin
...
SNARF vports.doc
SNARF weaks.doc
SNARF posix.doc
SNARF net_db.doc