Thanks for the info. Do you mind if I copy some of this information back to
the go-sqlite3 issues?
On Tue, Oct 4, 2016 at 1:27 PM Richard Hipp wrote:
On 10/4/16, Judson Lester wrote:
>
> That said, it's harmless until the deprecation turns into a removal at the
> OS level, at which point ignori
On 10/4/16, Judson Lester wrote:
> Thanks for the info. Do you mind if I copy some of this information back to
> the go-sqlite3 issues?
I do not mind.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.or
On 10/4/16, Judson Lester wrote:
>
> That said, it's harmless until the deprecation turns into a removal at the
> OS level, at which point ignoring the error becomes a sudden
> incompatibility with SQLite bindings.
>
Engineers at Apple tell me that they are still using
OSAtomicCompareAndSwapPtrBa
I can't prevent it being output as a consumer of the Go library. I've
needed to invest effort into my build chain to filter the warning; so
there's been some amount of pointless labor as a consequence. It might be
possible for the go-sqlite3 author to update the build commands to suppress
it?
All
Thanks very much. The warning itself recommends
atomic_compare_exchange_strong(),
but I can't tell you much more than that.
Would you be so kind as to let me know when/if there's a SQLite ticket for
this so that I can link it back to the project I encountered this in? It'll
help in terms of that m
On 10/4/16, Judson Lester wrote:
>
> Would you be so kind as to let me know when/if there's a SQLite ticket for
> this so that I can link it back to the project I encountered this in?
It's a harmless warning. *Harmless*. Can you not simply ignore it?
--
D. Richard Hipp
d...@sqlite.org
___
On 10/1/16, David Goldwich wrote:
> On Sat, Oct 1, 2016 at 4:41 PM, Simon Slavin wrote:
>> According to a 2012 post from DRH, try this compilation option:
>>
>> -DSQLITE_WITHOUT_ZONEMALLOC
>
> Another, probably better way would be -DOSATOMIC_USE_INLINED=1. That
> will transparently substitute leg
I understand that this project doesn't produce go-sqlite3, but the
sqlite-bindings.c that project incorporates (and which is the origin of the
deprecation warning) do seem to be part of this project. If that's not so,
can you direct me to the true source so I can raise the issue there?
On Sat, Oct
On Sat, Oct 1, 2016 at 4:41 PM, Simon Slavin wrote:
> According to a 2012 post from DRH, try this compilation option:
>
> -DSQLITE_WITHOUT_ZONEMALLOC
Another, probably better way would be -DOSATOMIC_USE_INLINED=1. That
will transparently substitute legacy atomic op interfaces with their
counterp
On 10/1/16, Judson Lester wrote:
> I understand that this project doesn't produce go-sqlite3, but the
> sqlite-bindings.c that project incorporates (and which is the origin of the
> deprecation warning) do seem to be part of this project. If that's not so,
> can you direct me to the true source so
According to a 2012 post from DRH, try this compilation option:
-DSQLITE_WITHOUT_ZONEMALLOC
Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Richard Hipp wrote:
> On 9/30/16, Judson Lester wrote:
>> vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:18709:17: warning:
>> 'OSAtomicCompareAndSwapPtrBarrier' is deprecated: first deprecated in macOS
>> 10.12 - Use atomic_compare_exchange_strong() from instead
>> [-Wdeprecated-declaratio
On 9/30/16, Judson Lester wrote:
> Using go-sqlite3, I get this warning with every build:
>
> # github.com/mattn/go-sqlite3
> vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:18709:17: warning:
> 'OSAtomicCompareAndSwapPtrBarrier' is deprecated: first deprecated in macOS
> 10.12 - Use atomic_c
Using go-sqlite3, I get this warning with every build:
# github.com/mattn/go-sqlite3
vendor/github.com/mattn/go-sqlite3/sqlite3-binding.c:18709:17: warning:
'OSAtomicCompareAndSwapPtrBarrier' is deprecated: first deprecated in macOS
10.12 - Use atomic_compare_exchange_strong() from instead
[-Wdep
14 matches
Mail list logo
