Added note about how to work around Fedora Core PYTHONPATH weirdness on X86_64.
authoreb <eb@221aa14e-8319-0410-a670-987f0aec2ac5>
Sat, 16 Sep 2006 02:14:47 +0000 (02:14 +0000)
committereb <eb@221aa14e-8319-0410-a670-987f0aec2ac5>
Sat, 16 Sep 2006 02:14:47 +0000 (02:14 +0000)
Closed ticket:39.

git-svn-id: http://gnuradio.org/svn/gnuradio/trunk@3544 221aa14e-8319-0410-a670-987f0aec2ac5

README

diff --git a/README b/README
index d2378f6bfac5e058323b8cf021b420dc3752b88a..9ecf7b0a605f40f3d756886b028f1da4d54c3092 100644 (file)
--- a/README
+++ b/README
@@ -196,6 +196,15 @@ installed version of python.
 
 You may want to add this to your ~/.bash_profile
 
+Note that on Fedora Core 4 and 5 when running on X86_64 machines,
+python is shippped with a strange (wrong) configuration that requires
+you to add both the lib64 and lib paths to your PYTHONPATH.
+E.g.,
+
+  $ export PYTHONPATH=/usr/local/lib64/python2.4/site-packages:/usr/local/lib/python2.4/site-packages
+
+[Don't complain to us, complain to the Fedora Core packagers.]
+
 
 Another handy trick if for example your fftw includes and libs are
 installed in, say ~/local/include and ~/local/lib, instead of