Zbigniew Baniewski wrote:
On Sat, Dec 15, 2007 at 12:48:44PM -0500, Robert L Cochran wrote:

I did a poor job of explaining this issue. GCC builds of 3.5.4 seem to fail. I've sent Richard a bunch of log files comparing source code builds of versions 3.5.3 and 3.5.4 showing what I believe are symptoms of the alleged failure. If anyone wants copies of the same set of files, feel free to contact me.

Just out of curiosity made a compilation of 3.5.4: apart of some warnings
(below) no errors at all.

cp: uwaga: plik źródłowy `./src/btree.h' pojawił się więcej niż raz
cp: uwaga: plik źródłowy `./src/hash.h' pojawił się więcej niż raz
cp: uwaga: plik źródłowy `./src/sqliteInt.h' pojawił się więcej niż raz
cp: uwaga: plik źródłowy `./src/vdbe.h' pojawił się więcej niż raz
cp: uwaga: plik źródłowy `./ext/fts1/fts1.h' pojawił się więcej niż raz
cp: uwaga: plik źródłowy `./ext/fts1/fts1_hash.h' pojawił się więcej niż raz
cp: uwaga: plik źródłowy `./ext/fts1/fts1_tokenizer.h' pojawił się więcej niż 
raz

(it means: "cp: warning: source file `......' appears more than once")

Compiled on:
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Linux with kernel 2.6.22
Pentium II


One additional comment:

Tcl's 8.5 "package require" isn't as tollerant about version marks, as in
8.4.x line it used to. So, the proper pgIndex.tcl contents should contain the
subversion digit as well, instead of just "3.5" - I mean:

package ifneeded sqlite3 3.5.4 [list load 
/usr/local/lib/tcl8.5/sqlite3/libtclsqlite3.so sqlite3]

Yes, I agree completely. 'make' wasn't issuing the 'creating sqlite3' message I've been so accustomed to, and the cp messages about duplicates concerned me. Christian supplied me some patches to get rid of the size messages and Richard told me they got rid of the creating message, 'make install' worked fine, and I have version 3.5.4 (with Christian's patches) running.

Bob

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to