>
>
> >>> I wonder if it's because of the bsd tar I used to tar it (I built that
> >> don't you have 'gtar' on your machine too?
>
I have `gnutar`, I guess. Maybe that should be added to the release
instructions as well...
> >> Probably my tar is newer and thus the install can live wit
On 2014-12-12, Dima Pasechnik wrote:
> On 2014-12-12, Dima Pasechnik wrote:
>> On 2014-12-12, kcrisman wrote:
>>> --=_Part_154_1466710874.1418353858850
>>> Content-Type: multipart/alternative;
>>> boundary="=_Part_155_44875405.1418353858850"
>>>
>>> --=_Part_155_44875405.1418353
On 2014-12-12, Dima Pasechnik wrote:
> On 2014-12-12, kcrisman wrote:
>> --=_Part_154_1466710874.1418353858850
>> Content-Type: multipart/alternative;
>> boundary="=_Part_155_44875405.1418353858850"
>>
>> --=_Part_155_44875405.1418353858850
>> Content-Type: text/plain; charset=U
On 2014-12-12, kcrisman wrote:
> --=_Part_154_1466710874.1418353858850
> Content-Type: multipart/alternative;
> boundary="=_Part_155_44875405.1418353858850"
>
> --=_Part_155_44875405.1418353858850
> Content-Type: text/plain; charset=UTF-8
>
>
>
>>Sage (6.4.1) notebook build
>Sage (6.4.1) notebook build failed on 32 bit CentOS 5.11. Version of
> sagenb was 0.11.1. To reproduce, build Sage from source (e.g., ./make from
> Sage installation directory). CPU was "CPU1: Intel(R) Core(TM)2 Duo CPU
> E4400 @ 2.00GHz stepping 0d" per dmesg. Sage runs, but ptest o
