On 18/01/2018 18:12, Ryan Schmidt wrote:
> Could you report this to the developers of libff so they can fix it?
>
> https://github.com/scipr-lab/libff/issues
Done.
https://github.com/scipr-lab/libff/issues/15
--
Red to red, black to black, switch it on, but stand well back.
On Jan 18, 2018, at 11:26, Bill Hill wrote:
>
> This failed with an error in deps/src/libff/libff/common/profiling.cpp
> complaining about this line :"::clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &ts)"
>
> Some flailing around on google and it seems that this function only exists in
> OSX 10.12 but
communication, but macports-development
> list should work as well.
>
> The sources for HomeBrew are probably here:
> https://github.com/ethereum/homebrew-ethereum
I've no idea about writing a port, but here's my notes on compiling ethereum
using macports. Just c
Hi Mojca,
Am Mittwoch, 17. Januar 2018, 11:11:09 CET schrieb Mojca Miklavec:
> To make it clear, it's perfectly OK if unexperienced users request new
> ports.
Thanks for your clearification - this was partly new to me. In my former
personal understanding and experiences macports "byself" contrib
On 17 January 2018 at 08:09, Niels Dettenbach (Syndicat IT & Internet)
via macports-users wrote:
> Am 17. Januar 2018 03:45:22 MEZ schrieb Terry Barnum :
>>(eth) with "brew install ethereum". I couldn't find geth, eth or
>>ethereum in macports. Any plans to
Am 17. Januar 2018 03:45:22 MEZ schrieb Terry Barnum :
>(eth) with "brew install ethereum". I couldn't find geth, eth or
>ethereum in macports. Any plans to add these?
I think there is a misunderstanding.
Macports contributions / ports usually come from the community - i.
I was poking around on Udemy looking at courses on ethereum smart contracts the
other night. One looked promising but watching the course preview video showed
setting up the dev environment with "brew tap ethereum/ethereum" and then
installing the Go (geth) and C++ clients (eth)
