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.
