I stumbled across a strange error when compiling sqlite, even trying to compile with gcc does not work.
The problem is created during the amalgation of sqlite3.c by the mksqlite3c.tcl script in the tool folder.
The sqlite3.c file created comments or breaks some code sections, leaves other comments as code.
Example of starting comment (see position of the /**)
Code: Select all
#if SQLITE_COVERAGE_T/**
"COVERAGE_TEST",
#endif
#if SQLITE_DEBUG
"DEBUG",
#endifCode: Select all
** <li>[[SQLITE_FCNTL_BUSYHANDLER]]
** ^The [SQLITE_FCNTL_BUSYHANDLER]
** file-control may be invoked by SQLite on the database file handle
** shortly after it is opened in order to provide a custom VFS with access
** to the connection's busy-handler callback. The argument is of type (void**)
** - an array of two (void *) values. The first (void *) actually points
** to a function of type (int (*)(void *)). In order to invoke the connection's
** busy-handler, this function should be invoked with the second (void *) in
**/**
"CO
#es the only argument. If it returns non-zero, then the operation
** should be retried. If it returns zero, the custom VFS should abandon the
** current operation.
**When triggering steps after step in ebuild, I can uncomment the triggering in the Makefile and copy the already amalgated file from the sqlite project (https://www.sqlite.org/2021/sqlite-amal ... 350500.zip).
It will compile then.
So what could cause such a weird behaviour of tcl?
Is someone else experience a similar issue whe compiling sqlite
