After renaming the libomalloc.so Successfully installed singular-3.1.7p1.p2
There were a bunch of warnings in the log but i guess that is okay... I'll try and build the rest now. On Friday, September 2, 2016 at 6:07:56 PM UTC+2, leif wrote: > > leif wrote: > > Simon Brandhorst wrote: > >> I did it triple-safe. > >> Doesn't seem to work. Here is the log. > > > > As guessed, the sizeof(long) test fails due to a runtime linker error. > > (Singular's 'configure' uses all libs found so far even in unrelated > > tests, and you seem to have some libomalloc system-wide which it picks > > up.) sizeof(long) should be set to 8 now though. > > > > So where does the build fail now? > > > > Could you move your libomalloc.so out of the way such that Singular > > won't find and try to use that? (It's supposed to build its own.) > > /In principle/ it should be sufficient to explicitly configure Singular > with '--enable-omalloc' (in build/pkgs/singular/spkg-install), but > AFAICS it still insists on (at least temporarily) picking up an existing > library, in your case in addition an apparently broken one. > > If you still have trouble building Singular (and if that's related to > the above), you can put another dumb patch (attached) into > build/pkgs/singular/patches/, then either running 'make' or doing > './sage -i -s singular', later continuing with 'make'. > > > By the way, Sage 7.4.beta3 has just been released, still with the old > Singular though. > > > -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.
