On Wed, 20 Jan 2010 16:21:55 Jonathan Bober wrote: > The Sage README.txt contains the text: > > "On Linux, if you get this error message: > > " restore segment prot after reloc: Permission denied " > > the problem is probably related to SELinux." > > I got this error on a machine on which I don't have root access, so I > couldn't try the suggested workarounds. Searching the Internet, I > decided that this might have something to do with the -fPIC compiler > option, so I changed the PARI spkg to make sure that PARI compiled with > -fPIC, and this fixed the problem. (I didn't save the original error > message, but it mentioned libpari-gmp.) > > Should PARI always be compiled with -fPIC? (Should I really be asking > this question to PARI developers who decided not to use PIC?) I don't > know much about this, but apparently -fPIC might cause some slowdown on > some systems. It seems that just about everything else in Sage is > compiled to be position independent, though (at least, nothing else > causes this problem). > For what it is worth on Gentoo Linux pari is build with -fPIC and we have no problem with it. In fact compiling a shared object without either -fPIC or -fpic (small difference, PIC is slower but supported everywhere, pic is faster but is not supported on all cpu, hence usually people default to PIC) is a QA problem as it lead to text relocation. I suppose a number of other distros shipping pari may force PIC/pic as well.
It probably should be enforced on platforms that support it at least, I don't remember what the equivalent is for solaris and so on. Francois
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
