leif wrote: > Simon Brandhorst wrote: >> So here are the logs. And a larger bit of the install.log > > Thanks, but we'd need the config.log files from Singular, not Sage's > top-level one, in your case: > > /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log > > and since omalloc takes an allegedly cached value for sizeof(long) from > Singular's top-level 'configure', where the value indeed appears to be > already wrong, probably also: > > /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.cache
Hmmm, I'd say there's a slight bug in Singular's top-level 'configure', as it doesn't really check for sizeof(long), but only cares whether it is 4 or not. If the test altogether fails, it doesn't bail out, but instead really sets the value (which is used later on) to 0. Simon, to figure out *why* the conftest failed, we still need the first file I mentioned above. -leif -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.