I'm curious: Why do you want to make SQLite untestable? On 4/24/17, Priebe, Sebastian <[email protected]> wrote: > Hello, > > shell.c fails to build with: > shell.c: In function 'do_meta_command': > shell.c:6442:50: error: 'sql_trace_callback' undeclared (first use in this > function) > sqlite3_trace_v2(p->db, SQLITE_TRACE_STMT, > sql_trace_callback,p->traceOut); > ^ > shell.c:6442:50: note: each undeclared identifier is reported only once for > each function it appears in > make: *** [sqlite3-shell.o] Error 1 > > Looking at the source code: the function sql_trace_callback is only > available if SQLITE_UNTESTABLE is not defined, but at the place it is used > there is no such restiction. > > Greetings > Sebastian > > > > > ------------------------------------------------------------------ > +++ CADCON ist Mitglied der SII Group +++ > Mehr auf unserer neuen Homepage > www.cadcon.de > ------------------------------------------------------------------- > > CADCON > Ingenieurgesellschaft mbH & Co. KG > Geschaeftsfuehrer: Robert Bauer > Sitz der Gesellschaft: 86368 Gersthofen > Registergericht: Amtsgericht Augsburg HRA 14521 > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
-- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
