leif wrote: > Francois Bissey wrote: >> >>> On 18/08/2016, at 19:38, Francois Bissey <[email protected]> >>> wrote: >>> >>> Stack smashing on 32bits >>> [dochtml] Setting permissions of DOT_SAGE directory so only you can read >>> and write it. >>> [dochtml] *** stack smashing detected ***: python terminated >>> [dochtml] >>> ------------------------------------------------------------------------ >>> [dochtml] >>> >>> I/We had to deal with that before, in singular, if memory serves me right. >>> >> >> Hum, was at linking time not run time. May have to inspect more carefully but >> -fno-stack-protector may come in handy somewhere. > > FWIW, attached are some excerpts from the log, with also some "funny" > errors I at least never noticed before. > > As you may already have seen, the crash starts somewhere in > sage/rings/number_field/totallyreal.so, goes through some > Singular-related extension modules up to sage/libs/singular/singular.so, > and "ends" in local/lib/libsingular.so. > > Compiler is Ubuntu's "native" GCC 4.8.4-2ubuntu1~14.04.3 > (--with-arch-32=i686 --with-tune=generic target=i686-linux-gnu), not > Sage's 4.9.3.
As expected, the last *successful* build on that machine was in May, for Sage *7.2*, and with SAGE_INSTALL_GCC=yes, i.e., using Sage's GCC 4.9.3, not Ubuntu's. -leif P.S.: The error in building NTL is also harmless; it happens during tuning (trying various different implementations, including such with inappropriate instructions). > > Build is in some VM on a 64-bit machine (Linux sagebu14_32s02 > 4.5.0-0.bpo.2-amd64 #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13) i686 i686 > i686 GNU/Linux). > > > -leif > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
