As I said, you can skip boringssl by setting gRPC_SSL_PROVIDER to none.
On Fri, Oct 7, 2016 at 11:02 PM, Robert Bielik <robert.bie...@gmail.com>
wrote:
> In the boringssl CMakeLists.txt file:
>
> if (NOT GO_EXECUTABLE)
> message(FATAL_ERROR "Could not find Go")
> endif()
>
> so, yes, the cmakelists build system requires Go.
>
>
> 2016-10-07 17:43 GMT+02:00 Nicolas Noble <nno...@google.com>:
>
>> Wait. The cmakefile itself doesn't require to have go. What's going on
>> exactly? Is it the cmakefile of boringssl which requires it? Define
>> gRPC_SSL_PROVIDER to none when calling or cmakefile and we won't include
>> anything.
>>
>> On Oct 7, 2016 07:31, "Robert Bielik" <robert.bie...@gmail.com> wrote:
>>
>>> Yes, true, but my whole project is CMake based and getting the Makefile
>>> generated stuff together with the rest in a cross compilation environment
>>> is something I'd hoped to avoid...
>>>
>>> 2016-10-07 16:29 GMT+02:00 Craig Tiller <ctil...@google.com>:
>>>
>>>> With the Makefile it should be fairly trivial to just build the
>>>> unsecure libs.
>>>>
>>>> On Fri, Oct 7, 2016 at 7:24 AM Robert Bielik <robert.bie...@gmail.com>
>>>> wrote:
>>>>
>>>>> Yes, I got into trouble fairly quickly. First off is the requirement
>>>>> for Go. I'm only planning using unsecure transport, is it possible to
>>>>> exclude boringssl ?
>>>>>
>>>>> 2016-10-07 16:19 GMT+02:00 Craig Tiller <ctil...@google.com>:
>>>>>
>>>>> Note that CMake is experimental and community supported at this point
>>>>> in time.
>>>>>
>>>>> On Fri, Oct 7, 2016 at 7:09 AM Robert Bielik <robert.bie...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Now that I see that there is added CMake support in v1.0.0, I'm
>>>>> heading there straight away!! :D
>>>>>
>>>>>
>>>>> Den fredag 7 oktober 2016 kl. 14:59:51 UTC+2 skrev Craig Tiller:
>>>>>
>>>>> How long until you can move to 1.0?
>>>>>
>>>>> Either way you should be able to squelch this error by setting the
>>>>> channel arg GRPC_ARG_ALLOW_REUSEPORT to 0.
>>>>>
>>>>> On Fri, Oct 7, 2016, 2:05 AM Robert Bielik <robert...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Nicolas,
>>>>>
>>>>> I ran our server with grpc log out, and there is an error:
>>>>>
>>>>> E0102 11:50:32.543620000 2923 tcp_server_posix.c:147] check for
>>>>> SO_REUSEPORT: {"created":"@129032.543473000","description":"SO_REUSEPORT
>>>>> unavailable on compiling system","file":"/home/osboxes/
>>>>> code/git/test/server/externals/grpc/src/core/lib/iomgr/socke
>>>>> t_utils_common_posix.c","file_line":175}
>>>>>
>>>>> I would expect this is the error, have no clue what it means :)
>>>>>
>>>>> gRPC version is: 0.14.0
>>>>>
>>>>> Regards
>>>>> /Robert
>>>>>
>>>>> 2016-10-06 20:21 GMT+02:00 Nicolas Noble <pixel...@gmail.com>:
>>>>>
>>>>> Before getting to the custom endpoint stuff, may I ask why the normal
>>>>> code doesn't work ? Maybe some subtle alterations to the current code
>>>>> might
>>>>> help. We haven't tested on every single flavor of Linux around, so maybe
>>>>> there's an oversight.
>>>>>
>>>>> On Wed, Oct 5, 2016 at 11:19 PM, Robert Bielik <robert...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> We have a customer for which the TCP endpoint seems not to work on
>>>>> their platform (ARMV7a based Linux), weird as that might be. So I'd like
>>>>> to
>>>>> look at implementing a custom endpoint to be used instead in such cases.
>>>>>
>>>>> Question is if there are examples for this ?
>>>>>
>>>>> Regards
>>>>> /Robert
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "grpc.io" group.
>>>>>
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to grpc-io+u...@googlegroups.com.
>>>>> To post to this group, send email to grp...@googlegroups.com.
>>>>>
>>>>>
>>>>> Visit this group at https://groups.google.com/group/grpc-io.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/grpc-io/047dae09-b5d9-4863
>>>>> -b062-eff5c3e75ce1%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/grpc-io/047dae09-b5d9-4863-b062-eff5c3e75ce1%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "grpc.io" group.
>>>>>
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to grpc-io+u...@googlegroups.com.
>>>>> To post to this group, send email to grp...@googlegroups.com.
>>>>>
>>>>>
>>>>> Visit this group at https://groups.google.com/group/grpc-io.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/grpc-io/CAEvHzA1NetQKg_Z4N
>>>>> oUT8tTanDYcHkGLSftYGs%3DNZrtfe%2BN_1g%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/grpc-io/CAEvHzA1NetQKg_Z4NoUT8tTanDYcHkGLSftYGs%3DNZrtfe%2BN_1g%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "grpc.io" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to grpc-io+unsubscr...@googlegroups.com.
>>>>> To post to this group, send email to grpc-io@googlegroups.com.
>>>>> Visit this group at https://groups.google.com/group/grpc-io.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/grpc-io/1516a83d-8521-4667
>>>>> -94c1-d51b737f69ff%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/grpc-io/1516a83d-8521-4667-94c1-d51b737f69ff%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "grpc.io" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to grpc-io+unsubscr...@googlegroups.com.
>>> To post to this group, send email to grpc-io@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/grpc-io.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/grpc-io/CAEvHzA0LuUujxBJb_DXQL9EiJCHJH_4RJcEbedV2pVSfvw_
>>> tBA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/grpc-io/CAEvHzA0LuUujxBJb_DXQL9EiJCHJH_4RJcEbedV2pVSfvw_tBA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
> --
> You received this message because you are subscribed to the Google Groups "
> grpc.io" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to grpc-io+unsubscr...@googlegroups.com.
> To post to this group, send email to grpc-io@googlegroups.com.
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/grpc-io/CAEvHzA0xDTd1ah-Q6R2qmi6WMvHbV-7nXAonhdmbpwPh1Q_4qg%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/grpc-io/CAEvHzA0xDTd1ah-Q6R2qmi6WMvHbV-7nXAonhdmbpwPh1Q_4qg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/CAEvr0PHZ3D3eZVnF1GjH7%2BmddpgD0cv6aes4j_oV_jYOXm%2B%2BWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
