On Tuesday, 29 December 2015 17:27:27 UTC-7, Volker Braun wrote: > > Hmm nDivBy is in libsingular which p_Procs_FieldQ does not link to. Though > thats not necessarily wrong. > > Whats the output of > > ldd local/bin/p_Procs_FieldQ.so > ldd local/lib/libsingular.so > sage -singular > > novoselt@sagenb:/var/opt/sage-7.0.beta1$ ldd local/bin/p_Procs_FieldQ.so linux-vdso.so.1 (0x00007ffe249c0000) libflint.so.13 => /home/novoselt/sage/local/lib/libflint.so.13 (0x00007f1e27658000) libmpfr.so.4 => /home/novoselt/sage/local/lib/libmpfr.so.4 (0x00007f1e273f8000) libmpir.so.16 => /home/novoselt/sage/local/lib/libmpir.so.16 (0x00007f1e27180000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f1e26e70000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f1e26b68000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f1e26950000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1e265a0000) libgmp.so.16 => /home/novoselt/sage/local/lib/libgmp.so.16 (0x00007f1e26328000) libntl.so.19 => /home/novoselt/sage/local/lib/libntl.so.19 (0x00007f1e25f10000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1e25cf0000) /lib64/ld-linux-x86-64.so.2 (0x00007f1e27f90000) libgf2x.so.1 => /home/novoselt/sage/local/lib/libgf2x.so.1 (0x00007f1e25ad8000) novoselt@sagenb:/var/opt/sage-7.0.beta1$ ldd local/lib/libsingular.so linux-vdso.so.1 (0x00007fff0d3f0000) libflint.so.13 => /home/novoselt/sage/local/lib/libflint.so.13 (0x00007f0dd5c08000) libmpfr.so.4 => /home/novoselt/sage/local/lib/libmpfr.so.4 (0x00007f0dd59a8000) libmpir.so.16 => /home/novoselt/sage/local/lib/libmpir.so.16 (0x00007f0dd5730000) libntl.so.19 => /home/novoselt/sage/local/lib/libntl.so.19 (0x00007f0dd5318000) libreadline.so.6 => /home/novoselt/sage/local/lib/libreadline.so.6 (0x00007f0dd50c8000) libgmp.so.16 => /home/novoselt/sage/local/lib/libgmp.so.16 (0x00007f0dd4e50000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0dd4b40000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0dd4838000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0dd4620000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0dd4270000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0dd4050000) /lib64/ld-linux-x86-64.so.2 (0x00007f0dd6a00000) libgf2x.so.1 => /home/novoselt/sage/local/lib/libgf2x.so.1 (0x00007f0dd3e38000) libtinfo.so.5 => /home/novoselt/sage/local/lib/libtinfo.so.5 (0x00007f0dd3c00000) novoselt@sagenb:/var/opt/sage-7.0.beta1$ ./sage -singular SINGULAR / Development A Computer Algebra System for Polynomial Computations / version 3-1-7 0< by: W. Decker, G.-M. Greuel, G. Pfister, H. Schoenemann \ Aug 2013 FB Mathematik der Universitaet, D-67653 Kaiserslautern \ > Auf Wiedersehen.
So it is still linked to the build place from which I've copied it. > On Wednesday, December 30, 2015 at 1:05:01 AM UTC+1, Andrey Novoseltsev > wrote: >> >> After building and moving to a different place I am now getting after >> banner when Sage starts: >> >> // ** Could not open dynamic library: >> /var/opt/sage-7.0.beta1/local/bin/p_Procs_FieldQ.so >> // ** Error message from system: >> /var/opt/sage-7.0.beta1/local/bin/p_Procs_FieldQ.so: undefined symbol: >> nDivBy >> // ** Singular will work properly, but much slower. >> // ** See the INSTALL section in the Singular manual for details. >> sage: >> >> There were no such issues with 6.10 or ever before. >> >> -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.