[jira] [Commented] (PROTON-1645) Building go binding with libuv fails

["Alan Conway (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PROTON-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212867#comment-16212867 ] 

Alan Conway commented on PROTON-1645:
-------------------------------------

Agreed. There are annoying problems both ways but I think I will switch it back to building in the build tree as this also causes problems with simultaneously building multiple build trees, as they compete to build in the same go output directory.

> Building go binding with libuv fails
> ------------------------------------
>
>                 Key: PROTON-1645
>                 URL: https://issues.apache.org/jira/browse/PROTON-1645
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: go-binding
>    Affects Versions: proton-c-0.18.0
>         Environment: Fedora 25, go 1.7.6, libuv 1.10.2
>            Reporter: Andrew Stitcher
>            Assignee: Alan Conway
>
> When proton-c is built with the libuv proactor the go binding build fails to link with:
> {noformat}
> [3/7] cd /home/andrew/Work/proton/bld-libuv && /...rew/Work/proton/src/examples/go/proton/broker.go
> FAILED: examples/go/CMakeFiles/go_example_proton_broker 
> cd /home/andrew/Work/proton/bld-libuv && /usr/bin/python /home/andrew/Work/proton/src/proton-c/env.py -- GOPATH=/home/andrew/Work/proton/src/proton-c/bindings/go CGO_CFLAGS=-I/home/andrew/Work/proton/src/proton-c/include\ -I/home/andrew/Work/proton/bld-libuv/proton-c/include CGO_LDFLAGS=-L/home/andrew/Work/proton/bld-libuv/proton-c PN_INTEROP_DIR=/home/andrew/Work/proton/src/tests/interop /usr/bin/go build -ldflags -r\ /home/andrew/Work/proton/bld-libuv/proton-c -o /home/andrew/Work/proton/bld-libuv/examples/go/proton/broker /home/andrew/Work/proton/src/examples/go/proton/broker.go
> # command-line-arguments
> /usr/lib/golang/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
> /usr/bin/ld: cannot find -lqpid-proton-core
> /usr/bin/ld: cannot find -lqpid-proton-core
> /usr/bin/ld: cannot find -lqpid-proton-core
> collect2: error: ld returned 1 exit status
> {noformat}
> From the error message it looks like go should have been passed the absolute path to {{libqpid-proton-core.so}} rather than just -lqpid-proton-core.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org