Darren Duncan wrote: > I would like to bring an apparent SQLite bug to the attention of the SQLite > core > developers as a ticket, where build fails on sun4-solaris-64int 2.10. > > This problem was reported to the DBD::SQLite (Perl binding) developers as an > automatically generated smoke tester ticket which can be seen here for all > the > details, but I have copied the most central portion into this email below the > dashed line: > > http://www.nntp.perl.org/group/perl.cpan.testers/2009/12/msg6529201.html > > Note that the DBD::SQLite version that was tested bundles SQLite 3.6.20, so > there is a chance that the latest 3.6.21 fixes it; if you think it necessary > I > can try asking the tester to try with the newer version. > > Thank you. > > -- Darren Duncan
I get the same warnings as Darren with Sun Studio - the Sun compiler tends to be more fussy than gcc. But my build does succeed. This is version 3.6.19 I assume. The output below is from a Sun Ultra 27 (Xeon processor), but I've built sqlite on Solaris 10 SPARC, from both the first version (02/2005) and the latest Solaris 10 update 7 (late 2009). /opt/sunstudio12.1/bin/cc "-DPACKAGE_NAME=\"sqlite\"" "-DPACKAGE_TARNAME=\"sqlite\"" "-DPACKAGE_VERSION=\"3.6.19\"" "-DPACKAGE_STRING=\"sqlite 3.6.19\"" "-DPACKAGE_BUGREPORT=\"http://www.sqlite.org\"" "-DPACKAGE=\"sqlite\"" "-DVERSION=\"3.6.19\"" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_READLINE=1 -I. -I. -I /export/home/drkirkby/sage-4.3/local/include -DSQLITE_THREADSAFE=1 -m64 -g -O2 -c sqlite3.c -KPIC -DPIC -o .libs/sqlite3.o "sqlite3.c", line 19207: warning: integer overflow detected: op "<<" "sqlite3.c", line 19224: warning: integer overflow detected: op "<<" "sqlite3.c", line 33277: warning: statement not reached "sqlite3.c", line 70955: warning: integer overflow detected: op "<<" /opt/sunstudio12.1/bin/cc "-DPACKAGE_NAME=\"sqlite\"" "-DPACKAGE_TARNAME=\"sqlite\"" "-DPACKAGE_VERSION=\"3.6.19\"" "-DPACKAGE_STRING=\"sqlite 3.6.19\"" "-DPACKAGE_BUGREPORT=\"http://www.sqlite.org\"" "-DPACKAGE=\"sqlite\"" "-DVERSION=\"3.6.19\"" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_FDATASYNC=1 -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_READLINE=1 -I. -I. -I /export/home/drkirkby/sage-4.3/local/include -DSQLITE_THREADSAFE=1 -m64 -g -O2 -c sqlite3.c -o sqlite3.o >/dev/null 2>&1 I do not know how much access sqlite developers have to Solaris machines, but if they need access to a SPARC, I can get a serious developer access to a T5240 via the University of Washington. Just drop me an email, with your preferred user name and state your role in sqlite development. Dave _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users