On 4/17/2013 08:06, Fulvio Esposito wrote:
I'm trying to use sqlite (tried 3.6 and the latest) in a project using
cygwin
I just released SQLite 3.7.16.2-1 to the Cygwin repo mirrors a few days
ago. If your mirror of choice is in sync, you can download it now.
Is there some reason you can't use that, or were you just not aware that
I'd finally gotten around to replacing the 3.7.13-1 release?
I cannot manage to compile it.
I didn't have any trouble on 32-bit Cygwin.
64-bit Cygwin required a bit of hand massaging before compilation since
upstream is shipping outdated autoconf outputs, however.
(Richard, if you're reading this, you should upgrade Automake to at
least 1.10. Previous releases don't understand 64-bit Cygwin, so we
have to replace config.guess. Additionally, Autoconf 2.69 doesn't like
some outdated constructs in your configure.ac file. If the syntax were
up to date, that would have allowed a second choice for fixing this
portability problem.)
sqlite3.c:30467: error: initializer element is not constant
sqlite3.c:30467: error: (near initialization for `aSyscall[0].pCurrent')
sqlite3.c:30467: error: initializer element is not constant
sqlite3.c:30467: error: (near initialization for `aSyscall[0]')
sqlite3.c:30479: error: initializer element is not constant
sqlite3.c:30479: error: (near initialization for `aSyscall[1]')
sqlite3.c:30487: error: initializer element is not constant
I'd guess you have a competing definition for the SYSCALL macro
somewhere. It's easy to test. Add this at line 30445:
#else
# error Fix your toolchain!
If you get the new error on retrying the compile, I'm right, and you
need to find out where it is and why it's being invoked.
Do you have multiple gcc's on your system? If so, are you *certain*
you're using Cygwin's gcc, and not, say, MinGW's, or some
cross-compilation toolchain?
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
