Thank you. I had forgotten to include the gcc "lib64" directory in my LD_LIBRARY_PATH. I have updated the appropriate module file. I will see what happens next.
Cindy On Monday, January 12, 2015 at 5:59:51 PM UTC-6, François wrote: > > It looks like something has gone wrong with LD_LIBRARY_PATH & co. This > means > that libstdc++ found when running sage is from older version of gcc than > the one used > to compile sage. Here you find libstdc++ from the system (gcc-4.3.4 I > presume) rather > than whatever you used to compile. > I assume you have a build environment that is different from the system > one (I have at > least 5 on the local power7 cluster). > > François > > On 13/01/2015, at 11:21, crook...@gmail.com <javascript:> wrote: > > > > Setting the effective group to the same as the group on the build > directory did allow pynac to compile. I am now stuck on an error in > > conway_polynomials-0.4.p0. > > > > ImportError: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not > found (required by > /hpc/tstapps/src/sage/sage-6.4.1/local/lib/python2.7/site-packages/sage/matrix/matrix_modn_dense_float.so) > > > > > > I have not had a chance to investigate, yet. It may be a couple of days > before I can get back to this. > > > > Cindy > > > > > > On Thursday, January 8, 2015 at 1:43:22 PM UTC-6, crook...@gmail.com > wrote: > > I am trying to compile sage-6.4.1 for one of my users. I am working on > a SLES11 SP2 machine using gcc 4.9.2 and python 2.7.7. I am using my > personal account and I own the build directory and all of the > directories/files for gcc and python. I am still getting the following > error: > > > > checking for a version of Python >= '2.1.0'... sys:1: RuntimeWarning: > not adding > > directory '' to sys.path since it's writable by an untrusted group. > > Untrusted users could put files in this directory which might then be > imported b > > y your Python code. As a general precaution from similar exploits, you > should no > > t execute Python code from this directory > > > > I have attached the sage_pynac-0.3.2.log for you to review. I have > tried looking through previous posts, but I don't see anything that quite > matches this situation. > > > > Thanks in advance for your help. > > > > Cindy > > > > On Thursday, January 8, 2015 at 1:43:22 PM UTC-6, crook...@gmail.com > wrote: > > I am trying to compile sage-6.4.1 for one of my users. I am working on > a SLES11 SP2 machine using gcc 4.9.2 and python 2.7.7. I am using my > personal account and I own the build directory and all of the > directories/files for gcc and python. I am still getting the following > error: > > > > checking for a version of Python >= '2.1.0'... sys:1: RuntimeWarning: > not adding > > directory '' to sys.path since it's writable by an untrusted group. > > Untrusted users could put files in this directory which might then be > imported b > > y your Python code. As a general precaution from similar exploits, you > should no > > t execute Python code from this directory > > > > I have attached the sage_pynac-0.3.2.log for you to review. I have > tried looking through previous posts, but I don't see anything that quite > matches this situation. > > > > Thanks in advance for your help. > > > > Cindy > > > > -- > > 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+...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > > Visit this group at http://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > On Monday, January 12, 2015 at 5:59:51 PM UTC-6, François wrote: > > It looks like something has gone wrong with LD_LIBRARY_PATH & co. This > means > that libstdc++ found when running sage is from older version of gcc than > the one used > to compile sage. Here you find libstdc++ from the system (gcc-4.3.4 I > presume) rather > than whatever you used to compile. > I assume you have a build environment that is different from the system > one (I have at > least 5 on the local power7 cluster). > > François > > On 13/01/2015, at 11:21, crook...@gmail.com <javascript:> wrote: > > > > Setting the effective group to the same as the group on the build > directory did allow pynac to compile. I am now stuck on an error in > > conway_polynomials-0.4.p0. > > > > ImportError: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not > found (required by > /hpc/tstapps/src/sage/sage-6.4.1/local/lib/python2.7/site-packages/sage/matrix/matrix_modn_dense_float.so) > > > > > > I have not had a chance to investigate, yet. It may be a couple of days > before I can get back to this. > > > > Cindy > > > > > > On Thursday, January 8, 2015 at 1:43:22 PM UTC-6, crook...@gmail.com > wrote: > > I am trying to compile sage-6.4.1 for one of my users. I am working on > a SLES11 SP2 machine using gcc 4.9.2 and python 2.7.7. I am using my > personal account and I own the build directory and all of the > directories/files for gcc and python. I am still getting the following > error: > > > > checking for a version of Python >= '2.1.0'... sys:1: RuntimeWarning: > not adding > > directory '' to sys.path since it's writable by an untrusted group. > > Untrusted users could put files in this directory which might then be > imported b > > y your Python code. As a general precaution from similar exploits, you > should no > > t execute Python code from this directory > > > > I have attached the sage_pynac-0.3.2.log for you to review. I have > tried looking through previous posts, but I don't see anything that quite > matches this situation. > > > > Thanks in advance for your help. > > > > Cindy > > > > On Thursday, January 8, 2015 at 1:43:22 PM UTC-6, crook...@gmail.com > wrote: > > I am trying to compile sage-6.4.1 for one of my users. I am working on > a SLES11 SP2 machine using gcc 4.9.2 and python 2.7.7. I am using my > personal account and I own the build directory and all of the > directories/files for gcc and python. I am still getting the following > error: > > > > checking for a version of Python >= '2.1.0'... sys:1: RuntimeWarning: > not adding > > directory '' to sys.path since it's writable by an untrusted group. > > Untrusted users could put files in this directory which might then be > imported b > > y your Python code. As a general precaution from similar exploits, you > should no > > t execute Python code from this directory > > > > I have attached the sage_pynac-0.3.2.log for you to review. I have > tried looking through previous posts, but I don't see anything that quite > matches this situation. > > > > Thanks in advance for your help. > > > > Cindy > > > > -- > > 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+...@googlegroups.com <javascript:>. > > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > > Visit this group at http://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
