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

memcpy build error with gcc >= 11.2 #12

Closed
catleeball opened this issue Jul 2, 2022 · 0 comments
Closed

memcpy build error with gcc >= 11.2 #12

catleeball opened this issue Jul 2, 2022 · 0 comments

Comments

@catleeball
Copy link

It looks like the sqlite package that Mabel uses currently has an issue open at crawshaw/sqlite#127 tracking this, but I thought I would post here for visibility if anyone else finds this error.

When building Mabel using gcc >= 11.2, the build fails with:

$ go install github.com/smmr-software/mabel@latest
# crawshaw.io/sqlite
In file included from /usr/include/string.h:535,
                 from go/pkg/mod/crawshaw.io/[email protected]/./c/sqlite3.c:14113,
                 from go/pkg/mod/crawshaw.io/[email protected]/static.go:19:
In function ‘memcpy’,
    inlined from ‘sqlite3Fts5IndexQuery’ at go/pkg/mod/crawshaw.io/[email protected]/./c/sqlite3.c:220863:18:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: warning: ‘__builtin_memcpy’ specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
   29 |   return __builtin___memcpy_chk (__dest, __src, __len,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   30 |                                  __glibc_objsize0 (__dest));
      |                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~

It looks like the issue was fixed in sqlite 3.38 and was merged into golang sqlite package in crawshaw/sqlite#133. It's currently live at head of the repository, but hasn't been released yet.

Just giving you a heads up so you can update your dependency on crawshaw/sqlite when it releases. :)

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

No branches or pull requests

1 participant