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 <graham.gerr...@gmail.com> wrote: > 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 Friday, 4 March 2016 09:33:11 UTC, Dima Pasechnik wrote: >> >> >> >> 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 differ between the 2 >>> installations...many more than I would have expected. Details available. >> >> >> Ah, it's 32-bit... >> it could be that the compiler toolchain is broken on your system. The >> 32-bit binary distribution isn't often tested nowadays, in particular not in >> the scenario you describe. >> >> >>> >>> >>> I shant be installing sage from source (too slow on a 32 bit system). I >>> would be willing to reinstall Ubuntu (which version?) and try a different >>> binary if that would help. >> >> >> our (only ?) 32-bit Linux box used for building sits open in my office, >> waiting for a new CPU fan. >> >> But it's not true that building is too slow - you can install system's >> distribution Atlas (or set SAGE_ATLAS_ARCH=base), then the rest will be >> built in 4-5 hours even on very old systems. (don't forget to 'export >> MAKE="make -j2"', or whatever the number of CPUs you have on the box, >> and then run $MAKE) >> >> http://doc.sagemath.org/html/en/installation/source.html#environment-variables >> (SAGE_ATLAS_LIB there) >> >> >> >> >>> >>> Would get a clean start! Have other users had success installing GAP >>> packages with this environment? >>> >>> Graham >>> >>> On Thursday, 3 March 2016 21:52:40 UTC, Dima Pasechnik wrote: >>>> >>>> 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, Alexander Konovalov wrote: >>>>> >>>>> 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 >>>>> package overview pages, e.g. like here: >>>>> http://www.gap-system.org/Packages/digraphs.html >>>>> >>>>> Hope this helps >>>>> Alexander >>>>> > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-support+unsubscr...@googlegroups.com. > To post to this group, send email to sage-support@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
