Thanks John
Supports the hypothesis that the problem is with 32 bit binary versions,
only.
Graham
On Monday, 7 March 2016 18:43:01 UTC, John Cremona wrote:
>
> I just completed my build from source of 7.0 on a 32-bit laptop
> running ubuntu 14.04, and all tests pass.
>
> ./sage -i database_
I just completed my build from source of 7.0 on a 32-bit laptop
running ubuntu 14.04, and all tests pass.
./sage -i database_gap -- all OK
./sage -i gap_packages -- all OK
Those are the only two gap packages I normally install.
John
On 4 March 2016 at 12:24, Graham Gerrard wrote:
> Dima
>
> L
Dima
Looks like I have more 32 bit systems than you! I am just about to pension
them off. One still runs Sage6.7 with GAP packages successfully added
under Ubuntu 12.04. Tried Sage7.0 12.04 version on this platform.
Problems are similar to 14.04. Supports your hypothesis.
Graham
On Fri
On Friday, March 4, 2016 at 12:07:51 AM UTC, Graham Gerrard wrote:
>
> Hi Dima
>
> Not urgent for me. I still have a perfectly good 64 bit version working,
> no problems.
>
> I am inclined towards the "weird behaviour of the 32 bit distribution".
> There is a huge numbers of filenames which d
Hi Dima
Not urgent for me. I still have a perfectly good 64 bit version working,
no problems.
I am inclined towards the "weird behaviour of the 32 bit distribution".
There is a huge numbers of filenames which differ between the 2
installations...many more than I would have expected. Details
Hi Alexander
Fairly certain that the packages I use do not have dependencies (as I have
just extracted them into the package directory in the past, with complete
success). However, packages I use are Repsn, loops, design (which requires
GRAPE if nauty is used) and database_gap (which does requ
This has nothing to do with GAP packages. It's some weird behaviour of a
binary Sage installation, that does not seem to have gcc available
(although it should?). It's evident from the attached log.
A short workaround is to install Sage from source.
On Thursday, March 3, 2016 at 9:25:50 PM UTC
Graham, which package would you like to install? Even if it uses no
compilation, it may depend on other GAP packages which should be installed
as well. Some of these may require compilation, some not. Dependencies are
described in PackageInfo.g file in the package root directory, and also on
pa
