Skip to Content.
Sympa Menu

cado-nfs - Re: [Cado-nfs-discuss] partal compile and sqlite3 error

Subject: Discussion related to cado-nfs

List archive

Re: [Cado-nfs-discuss] partal compile and sqlite3 error


Chronological Thread 
  • From: Emmanuel Thomé <Emmanuel.Thome@inria.fr>
  • To: paul zimmermann <Paul.Zimmermann@inria.fr>
  • Cc: cado-nfs-discuss@lists.gforge.inria.fr
  • Subject: Re: [Cado-nfs-discuss] partal compile and sqlite3 error
  • Date: Fri, 22 Jul 2016 15:26:45 +0200
  • List-archive: <http://lists.gforge.inria.fr/pipermail/cado-nfs-discuss/>
  • List-id: A discussion list for Cado-NFS <cado-nfs-discuss.lists.gforge.inria.fr>

On Tue, Jul 19, 2016 at 09:50:07AM +0200, Paul Zimmermann wrote:
> please only report bugs for ***releases*** of CADO-NFS, the development
> version is not guaranteed to work, or even compile.

This is true, but only to a certain extent. Feedback is also welcome on
the development version. Sometimes (e.g. when the released version ages
a bit), it becomes even the primary feedback topic we're interested in...


Now specifically, for these warnings:

> > /home/yangm/rsa1024/cado-nfs/linalg/bwc/matmul-basicp.cpp:40: error:
> > using ‘typename’ outside of template

This was a typo, and was fixed by f501ed8 two weeks ago.

> > Critical:Database: sqlite3 reports error accessing the database.
> > Critical:Database: Database file may have gotten corrupted, or maybe
> > filesystem does not
> > properly support file locking.
[...]
> > sqlite3.OperationalError: disk I/O error

Whatever you observe which ends up with something like "disk I/O error"
certainly hints at cado-nfs *NOT* being the culprit. Perhaps there's a
point, in this case, in looking at what your operating system says about
the health of the data volume on which your database resides.

E.




Archive powered by MHonArc 2.6.19+.

Top of Page