Nah, it's not that - https://travis-ci.org/miracl/gomiracl/jobs/345158452.
If fails also in golang:latest where the yaml gotcha it's not a thing.
Solid suggestion though, thanks.
On Friday, February 23, 2018 at 11:02:59 AM UTC+2, Владислав Митов wrote:
>
> Ah, I read about that
quot;`
>
> So your build is building with go 1.1 instead of 1.10.
>
> Ran into this myself this morning.
>
> -Nic
>
> On Thursday, February 22, 2018 at 11:38:43 AM UTC-5, Владислав Митов wrote:
>>
>> Hey guys,
>>
>> One of my build started failing w
UTC+2, Ian Lance Taylor wrote:
>
> On Thu, Feb 22, 2018 at 8:38 AM, Владислав Митов
> > wrote:
> >
> > One of my build started failing with 1.10. Basically I'm building a
> wrapper
> > around a C library and it fails with:
> >
Hey guys,
One of my build started failing with 1.10. Basically I'm building a wrapper
around a C library and it fails with:
# runtime/cgo
gcc_libinit.c: In function '_cgo_try_pthread_create':
gcc_libinit.c:97:18: error: storage size of 'ts' isn't known
struct timespec ts;
^
ember 29, 2017 at 3:12:31 PM UTC-8, xingtao zhao wrote:
>>
>> Make your C function to accept octet parameter, instead of *octet parameter?
>> Then there will be no allocations.
>>
>> On Wednesday, November 29, 2017 at 2:39:38 PM UTC-8, Владислав Митов
>> wrote:
>>&g
So no way around 4 allocations for 2 values?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit ht
Hey, thanks about the swift answer.
I got to that thread but the solutions didn't worked for me. I'm still hitting
the cgo pointer check. Works if I disable it though.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this grou
Hello,
I'm writing a Go wrapper around C library and I'm trying to omit all
possible allocations.
Here is my working example
-
https://github.com/milagro-crypto/milagro-crypto-c/commit/1f070f24d83c76c5e7e5c6c548a9715438abc758#diff-a3c034fc3f075297e9e3a7cca9ace62eR65.
There are 3 allocations t
