On OSX we don't build our own sqlite as that tends to conflict with the
OSX-provided version.
On Thursday, April 2, 2015 at 4:36:03 PM UTC+2, David Einstein wrote:
>
> I'm beginning to understand what is wrong. A couple of years ago I must
> have overwritten the default python 2.7 with someth
I'm beginning to understand what is wrong. A couple of years ago I must
have overwritten the default python 2.7 with something newer (I have vague
recollections of needing it to get scipy working). A stupid thing to do,
and I should know better.
Now _sqlite3 is in
/System/Library/Framework
On Tuesday, March 31, 2015 at 1:03:08 PM UTC-7, David Einstein wrote:
>
> When building python it does complain about not finding _sqlite3 along with
>
> _bsddb _sqlite3 _ssl
> bsddb185 dbmdl
> gdbm imageop
When building python it does complain about not finding _sqlite3 along with
_bsddb _sqlite3 _ssl
bsddb185 dbmdl
gdbm imageoplinuxaudiodev
nisossaudiodevspwd
su
On Tuesday, March 31, 2015 at 11:31:42 AM UTC-7, David Einstein wrote:
>
> The sqlite package seems to have installed correctly. Log attached.
>
On OS X, Sage's sqlite package just creates a link to the pre-existing file
/usr/bin/sqlite3. The error mentioned "_sqlite3", which is a Python modul
The sqlite package seems to have installed correctly. Log attached.
I am guilty of having a homebrew sqlite (It was quarantined in the Cellar)
I have removed it and will try to recompile from scratch.
Found local metadata for sqlite-3.8.4.3
Attempting to download package sqlite-3.8.4.3
>>> Tryi
Whats in your sqlite and python compile log (in $SAGE_ROOT/logs/pkgs)?
Do you have another conflicting sqlite install in /usr/local, e.g. homebrew
and friends?
On Tuesday, March 31, 2015 at 7:51:58 PM UTC+2, David Einstein wrote:
>
> When attempting to compile sage from source on my laptop it
