The string "integer value too large to represent" is not found in 
sqlite sources, so I assume it is an error in either in Tcl or the tcl 
test harness.

I have no idea why the checksum of the databases in malloc2-1.1.28.5
is different, or whether it is harmless.

As for the malloc2.1.5 failure, as far as I can tell looking at the test, 
an empty abc table should be present.

I have no idea about lock4-1.3.

I'd suggest to make a ticket for each of these test errors.

  http://www.sqlite.org/cvstrac/tktnew

--- Victor Secarin <[EMAIL PROTECTED]> wrote:
> Here are the fulltest errors I get trying to build sqlite 3.4.1 with the 
> included gcc on Enterprise 3, 4 and Fedora 5.
> After building tcl8.4.7 and installing it in /usr/local, I was able to 
> configure with "--with-tcl=/usr/local/lib" and build the two libraries 
> completely and then run the fulltest on Enterprise 3 as well.
> I hope someone will find these useful and will be able to tell me to 
> what extent the builds may be used or not.
> Meanwhile, I will redo these builds, wit the Intel 9.1.052 compiler this 
> time, and I will post the fulltest results.
> Please advise, and thank you very much,
> Victor Secarin
> 
> 
> A. Fulltest on Fedora 5 (64 bits) with glibc-2.4-11/gcc-4.1.1:
> ===========================================
> 3 errors out of 240587 tests
> Failures on these tests: lock4-1.3 malloc2-1.1.28.5 malloc2.1.5
> 
> lock4-1.3...
> Error: database is locked
> malloc2-1.1.28.5...
> Expected: [7150405b58e993f161c43b93edd13553]
>      Got: [bc598bca7e7514b7f36e3e3d178a97ba]
> malloc2.1.5...
> Error: no such table: abc
> 
> B. Fulltest on RedHat Enterprise 4 update 5 (64 bits) with 
> glibc-2.3.4-2.36/gcc-3.4.4:
> ============================================================
> 2 errors out of 127702 tests
> Failures on these tests: printf-8.1 printf-8.2
> 
> printf-8.1...
> Error: integer value too large to represent
> printf-8.2...
> Error: integer value too large to represent
> ====================================
> 
> C. Fulltest on Enterprise 3  update 9 (64 bits) with 
> glibc-2.3.2-95.50/gcc-3.2.3:
> =======================================================
> 2 errors out of 127702 tests
> Failures on these tests: printf-8.1 printf-8.2
> 
> printf-8.1...
> Error: integer value too large to represent
> printf-8.2...
> Error: integer value too large to represent
> 
> 
> D. Fulltest on Enterprise 3  update 9 (32 bits) with 
> glibc-2.3.2-95.50/gcc-3.2.3:
> ========================================================
> 3 errors out of 110199 tests
> Failures on these tests: lock4-1.3 malloc2-1.1.34.5 malloc2.1.5
> 
> lock4-1.3...
> Error: database is locked
> malloc2-1.1.34.5...
> Expected: [7150405b58e993f161c43b93edd13553]
>      Got: [bc598bca7e7514b7f36e3e3d178a97ba]
> malloc2.1.5...
> Error: no such table: abc
> 
> 
> please advise, and thank you very much,
> Victor Secarin
> 
> 
> Joe Wilson wrote:
> > Can you post the output for the failed tests?
> >
> > i.e.:
> >
> >  footest-13.1...
> >  Expected: [10]
> >       Got: [0]
> >
> > --- Victor Secarin <[EMAIL PROTECTED]> wrote:
> >   
> >> Hello, everyone. I just started to look at the software and I have two 
> >> questions:
> >>     
> >>> Question 1:
> >>> ========
> >>> Building sqlite-3.4.1, as obtained from the cvs, on Fedora 5, 64 bits, 
> >>> with gcc 4.1.1, over glibc-2.4-11, and tcl/tcl-devel 8.4.13-1.1,
> >>> followed by "make fulltest", I get the following three failed tests:
> >>>
> >>> lock4-1.3  malloc2-1.1.31.5  malloc2.1.5
> >>>
> >>>
> >>> Building the same with the Intel compiler icc 9.1.051, I get 8 failures 
> >>> as follows:
> >>>
> >>> bind-4.4  bind-4.5  expr-2.26  malloc2.1.5  printf-13.6  utf16-bind-4.4  
> >>> utf16-bind-4.5  utf16-expr-2.26



       
____________________________________________________________________________________
Got a little couch potato? 
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
 

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

Reply via email to