" --with-pythondir=/usr/lib64" didn't work for me. I think the problem is that the configure script don't care about "--with-libsuffix=64" when it comes to python. "--with-pythondir" changes the $ac_python_dir variable in the configure script. As you can see in the line below from configure, thats no good: python_libdirs="$ac_python_dir/lib /usr/lib /usr/local /usr/lib $kde_extra_libs" changing this line to (should be on a single line): python_libdirs="$ac_python_dir/lib64 /usr/lib64 /usr/local /usr/lib64 $kde_extra_libs" makes it work for me. There are probably better solutions but anyway this works. Note that there are about 15 of this line in the configure script. /Arne On 8.3 2005 05:49, Joe Morris (NTM) wrote:
David wrote:
I have exactly the same problem. When I do the ./configure this is on the Python line. ================================= checking for Python directory... /usr/local checking for Python2.3... header /usr/include/python2.3 library no modules no ================================= You need --with-pythondir=/usr/lib64 -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
------------------------------------------------------------------ Gratis svenskpråkig e-post och förmånliga textmeddelanden http://webmail.surfnet.fi ------------------------------------------------------------------
Thank's Arne. I'll give that a try next. David Arne wrote:
" --with-pythondir=/usr/lib64" didn't work for me. I think the problem is that the configure script don't care about "--with-libsuffix=64" when it comes to python. "--with-pythondir" changes the $ac_python_dir variable in the configure script. As you can see in the line below from configure, thats no good:
python_libdirs="$ac_python_dir/lib /usr/lib /usr/local /usr/lib $kde_extra_libs"
changing this line to (should be on a single line): python_libdirs="$ac_python_dir/lib64 /usr/lib64 /usr/local /usr/lib64 $kde_extra_libs"
makes it work for me. There are probably better solutions but anyway this works. Note that there are about 15 of this line in the configure script.
/Arne
On 8.3 2005 05:49, Joe Morris (NTM) wrote:
David wrote:
I have exactly the same problem. When I do the ./configure this is on the Python line. ================================= checking for Python directory... /usr/local checking for Python2.3... header /usr/include/python2.3 library no modules no =================================
You need --with-pythondir=/usr/lib64 -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
------------------------------------------------------------------ Gratis svenskpråkig e-post och förmånliga textmeddelanden http://webmail.surfnet.fi ------------------------------------------------------------------
Thanks Arne. It works for me. On Tue, 2005-03-08 at 11:12 +0200, Arne wrote:
" --with-pythondir=/usr/lib64" didn't work for me. I think the problem is that the configure script don't care about "--with-libsuffix=64" when it comes to python. "--with-pythondir" changes the $ac_python_dir variable in the configure script. As you can see in the line below from configure, thats no good:
python_libdirs="$ac_python_dir/lib /usr/lib /usr/local /usr/lib $kde_extra_libs"
changing this line to (should be on a single line): python_libdirs="$ac_python_dir/lib64 /usr/lib64 /usr/local /usr/lib64 $kde_extra_libs"
makes it work for me. There are probably better solutions but anyway this works. Note that there are about 15 of this line in the configure script.
Thank's Arne. I made the changes you suggested to the configure script and everything worked pretty much as it should. David Arne wrote:
" --with-pythondir=/usr/lib64" didn't work for me. I think the problem is that the configure script don't care about "--with-libsuffix=64" when it comes to python. "--with-pythondir" changes the $ac_python_dir variable in the configure script. As you can see in the line below from configure, thats no good:
python_libdirs="$ac_python_dir/lib /usr/lib /usr/local /usr/lib $kde_extra_libs"
changing this line to (should be on a single line): python_libdirs="$ac_python_dir/lib64 /usr/lib64 /usr/local /usr/lib64 $kde_extra_libs"
makes it work for me. There are probably better solutions but anyway this works. Note that there are about 15 of this line in the configure script.
/Arne
On 8.3 2005 05:49, Joe Morris (NTM) wrote:
David wrote:
I have exactly the same problem. When I do the ./configure this is on the Python line. ================================= checking for Python directory... /usr/local checking for Python2.3... header /usr/include/python2.3 library no modules no =================================
You need --with-pythondir=/usr/lib64 -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
------------------------------------------------------------------ Gratis svenskpråkig e-post och förmånliga textmeddelanden http://webmail.surfnet.fi ------------------------------------------------------------------
Thank's Arne. I made the changes you suggested to the configure script and everything worked pretty much as it should.
Arne wrote:
" --with-pythondir=/usr/lib64" didn't work for me. Made me do some checking. On 8.3 2005 05:49, Joe Morris (NTM) wrote:
David wrote:
I have exactly the same problem. When I do the ./configure this is on the Python line. ================================= checking for Python directory... /usr/local checking for Python2.3... header /usr/include/python2.3 library no modules no =================================
You need --with-pythondir=/usr/lib64 I had a typo that might be of interest since I have seen the same kind of thing in configure script (hard coded to lib not lib64 directories). There was a typo in my spec file that made the line --with-pythondir=/usr/lib64 /usr instead of just /usr/lib64. If passed
David wrote: that way (i.e. 2 directories), it does find python modules and compiles fine. This might come in handy for other broken configure scripts. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
David wrote:
Thank's Arne. I made the changes you suggested to the configure script and everything worked pretty much as it should.
Arne wrote:
" --with-pythondir=/usr/lib64" didn't work for me.
Made me do some checking.
On 8.3 2005 05:49, Joe Morris (NTM) wrote:
David wrote:
I have exactly the same problem. When I do the ./configure this is on the Python line. ================================= checking for Python directory... /usr/local checking for Python2.3... header /usr/include/python2.3 library no modules no =================================
You need --with-pythondir=/usr/lib64
I had a typo that might be of interest since I have seen the same kind of thing in configure script (hard coded to lib not lib64 directories). There was a typo in my spec file that made the line --with-pythondir=/usr/lib64 /usr instead of just /usr/lib64. If passed that way (i.e. 2 directories), it does find python modules and compiles fine. This might come in handy for other broken configure scripts. HTH.
Very interesting. I will try and remember that one. D
Hi, I have a quad processor Opteron machine with SLES9 installed and that reboots about once every hour after cron.hourly is run. Looking in corn.hourly I see that "mcelog" is the only thing run here. Looking in /var/log/mcelog I get messages like the following: MCE 0 CPU 0 BANK 4 TSC 3cea13080d266 ADDR a98b0538 STATUS 9474c00100000813 MCGSTATUS 0 MCE 0 CPU 2 BANK 4 TSC 70a3e89bae5c6 ADDR 523748358 STATUS 946cc00100000813 MCGSTATUS 0 MCE 1 CPU 2 BANK 4 TSC 70ae68df9e742 ADDR 523748358 STATUS 946cc00100000813 MCGSTATUS 0 MCE 2 CPU 2 BANK 4 TSC 70b8e925da516 ADDR 523748358 STATUS 946cc00100000813 MCGSTATUS 0 MCE 3 CPU 2 BANK 4 TSC 71026b0a9814b ADDR 523748358 STATUS 946cc00100000813 MCGSTATUS 0 Parsing the MCE messages gives me the following ./parsemce -e 62680aa4f40e6 -a 523748340 -b 0 -s 946cc00000000833 Status: (62680aa4f40e6) Machine Check in progress. Error IP valid Restart IP invalid. parsebank(0): 946cc00000000833 @ 523748340 External tag parity error Correctable ECC error Address in addr register valid Error enabled in control register Bus and interconnect error Participation: Local processor originated request Timeout: Request did not timeout Request: Generic error Transaction type : Instruction Memory/IO : Other The machine is based on a Tyan 4882 MB with BIOS 1.03. It has 4 850 CPUs and 32 GB of Crucial DDR400 memory (2GB modules). What do you think is the problem? Memory? CPU? BIOS? /peter
participants (5)
-
Arne -
David -
Joe Morris (NTM) -
Marios K. -
Peter Rundberg