Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go-sqlite3 still using built-in copy despite libsqlite3 tag #330

Closed
stgraber opened this issue Sep 21, 2016 · 2 comments · Fixed by #339
Closed

go-sqlite3 still using built-in copy despite libsqlite3 tag #330

stgraber opened this issue Sep 21, 2016 · 2 comments · Fixed by #339

Comments

@stgraber
Copy link
Contributor

Building with -tags libsqlite3, while it does seem to be using the sqlite3.h from the system, still appears to be using the built-in copy of the actual code rather than linking against the system library.

stgraber@castiana:~/data/code/go/src/github.com/mattn/go-sqlite3 (master)$ go build -tags libsqlite3 _example/simple/simple.go
stgraber@castiana:~/data/code/go/src/github.com/mattn/go-sqlite3 (master)$ ldd simple | grep sqlite

Now if I actually remove the embedded copy and try again (no other changes):

stgraber@castiana:~/data/code/go/src/github.com/mattn/go-sqlite3 (master)$ rm sqlite3-binding.*
stgraber@castiana:~/data/code/go/src/github.com/mattn/go-sqlite3 (master)$ go build -tags libsqlite3 _example/simple/simple.go
stgraber@castiana:~/data/code/go/src/github.com/mattn/go-sqlite3 (master)$ ldd simple | grep sqlite
        libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f8ba57ea000)

Any idea what's going on?

@leehambley
Copy link

I think this is a duplicate of #318 (comment) having reviewed some of the other issues related to -tag libsqlite3

@mattn
Copy link
Owner

mattn commented Sep 27, 2016

This is related on this. #294

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants