diff options
| author | Guido van Rossum <guido@python.org> | 1996-10-13 15:48:56 +0000 | 
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 1996-10-13 15:48:56 +0000 | 
| commit | 9c5dc29c3d1d5dc18bd7a4a2cd63c6e8abd031ea (patch) | |
| tree | 32c9e0315629310c1f58e56976855930fc105db7 | |
| parent | 084814624df0c63a95d5e7f9eb2c83ca06d4a5bd (diff) | |
| download | cpython-git-9c5dc29c3d1d5dc18bd7a4a2cd63c6e8abd031ea.tar.gz | |
Added item about bug in Slackware96 libdl.
| -rw-r--r-- | Misc/FAQ | 49 | 
1 files changed, 30 insertions, 19 deletions
| @@ -10,7 +10,7 @@ Approved: news-answers-request@MIT.Edu  Archive-name: python-faq/part1  Submitted-by: Guido van Rossum <guido@cnri.reston.va.us>  Version: $Revision$ -Last-modified: 11 September 1996 +Last-modified: $Date$  This article contains answers to Frequently Asked Questions about  Python (an object-oriented interpreted programming language -- see @@ -105,16 +105,17 @@ Here's an overview of the questions per chapter:    3.9. Q. Trouble with prototypes on Ultrix.    3.10. Q. Other trouble building Python on platform X.    3.11. Q. How to configure dynamic loading on Linux. -  3.12. Q. Errors when linking with a shared library containing C++ code. -  3.13. Q. I built with tkintermodule.c enabled but get "Tkinter not found". -  3.14. Q. I built with Tk 4.0 but Tkinter complains about the Tk version. -  3.15. Q. Link errors for Tcl/Tk symbols when linking with Tcl/Tk. -  3.16. Q. I configured and built Python for Tcl/Tk but "import Tkinter" +  3.12. Q: I can't get shared modules to work on Linux 2.0 (Slackware96)? +  3.13. Q. Errors when linking with a shared library containing C++ code. +  3.14. Q. I built with tkintermodule.c enabled but get "Tkinter not found". +  3.15. Q. I built with Tk 4.0 but Tkinter complains about the Tk version. +  3.16. Q. Link errors for Tcl/Tk symbols when linking with Tcl/Tk. +  3.17. Q. I configured and built Python for Tcl/Tk but "import Tkinter"          fails. -  3.17. Q. Tk doesn't work right on DEC Alpha. -  3.18. Q. Several common system calls are missing from the posix module. -  3.19. Q. ImportError: No module named string, on MS Windows. -  3.20. Q. Core dump on SGI when using the gl module. +  3.18. Q. Tk doesn't work right on DEC Alpha. +  3.19. Q. Several common system calls are missing from the posix module. +  3.20. Q. ImportError: No module named string, on MS Windows. +  3.21. Q. Core dump on SGI when using the gl module.   4. Programming in Python    4.1. Q. Is there a source code level debugger with breakpoints, step, @@ -776,13 +777,23 @@ it to me too.  A. This is now automatic as long as your Linux version uses the ELF  object format (all recent Linuxes do). -3.12. Q. Errors when linking with a shared library containing C++ code. +3.12. Q: I can't get shared modules to work on Linux 2.0 (Slackware96)? + +A: This is a bug in the Slackware96 release.   The fix is simple: + +Make sure that there is a link from /lib/libdl.so to /lib/libdl.so.1 +so that the following links are setup: + +	/lib/libdl.so -> /lib/libdl.so.1 +	/lib/libdl.so.1 -> /lib/libdl.so.1.7.14 + +3.13. Q. Errors when linking with a shared library containing C++ code.  A. Link the main Python binary with C++.  Change the definition of  LINKCC in Modules/Makefile to be your C++ compiler.  You may have to  edit config.c slightly to make it compilable with C++. -3.13. Q. I built with tkintermodule.c enabled but get "Tkinter not found". +3.14. Q. I built with tkintermodule.c enabled but get "Tkinter not found".  A. Tkinter.py (note: upper case T) lives in a subdirectory of Lib,  Lib/tkinter.  If you are using the default module search path, you @@ -790,7 +801,7 @@ probably didn't enable the line in the Modules/Setup file defining  TKPATH; if you use the environment variable PYTHONPATH, you'll have to  add  the proper tkinter subdirectory. -3.14. Q. I built with Tk 4.0 but Tkinter complains about the Tk version. +3.15. Q. I built with Tk 4.0 but Tkinter complains about the Tk version.  A. Several things could cause this.  You most likely have a Tk 3.6  installation that wasn't completely eradicated by the Tk 4.0 @@ -801,7 +812,7 @@ have compiled Python with the old tk.h header file (yes, this actually  compiles!); you may actually have linked with Tk 3.6 even though Tk  4.0 is also around.  Similar for Tcl 7.4 vs. Tcl 7.3. -3.15. Q. Link errors for Tcl/Tk symbols when linking with Tcl/Tk. +3.16. Q. Link errors for Tcl/Tk symbols when linking with Tcl/Tk.  Quite possibly, there's a version mismatch between the Tcl/Tk header  files (tcl.h and tk.h) and the tck/tk libraries you are using (the @@ -812,13 +823,13 @@ Setup line for _tkinter in some Python distributions references  7.4/4.0 by default.  Changing this to 7.5/4.1 should take care of  this. -3.16. Q. I configured and built Python for Tcl/Tk but "import Tkinter" +3.17. Q. I configured and built Python for Tcl/Tk but "import Tkinter"  fails.  A. Most likely, you forgot to enable the line in Setup that says  "TKPATH=:$(DESTLIB)/tkinter". -3.17. Q. Tk doesn't work right on DEC Alpha. +3.18. Q. Tk doesn't work right on DEC Alpha.  A. You probably compiled either Tcl, Tk or Python with gcc.  Don't.  For this platform, which has 64-bit integers, gcc is known to generate @@ -830,7 +841,7 @@ far as we know, there are no problem with gcc on other platforms --  the instabilities seem to be restricted to the DEC Alpha.)  See also  question 3.6. -3.18. Q. Several common system calls are missing from the posix module. +3.19. Q. Several common system calls are missing from the posix module.  A. Most likely, *all* test compilations run by the configure script  are failing for some reason or another.  Have a look in config.log to @@ -838,7 +849,7 @@ see what could be the reason.  A common reason is specifying a  directory to the --with-readline option that doesn't contain the  libreadline.a file. -3.19. Q. ImportError: No module named string, on MS Windows. +3.20. Q. ImportError: No module named string, on MS Windows.  A. Most likely, your PYTHONPATH environment variable should be set to  something like: @@ -847,7 +858,7 @@ set PYTHONPATH=c:\python;c:\python\lib;c:\python\scripts  (assuming Python was installed in c:\python) -3.20. Q. Core dump on SGI when using the gl module. +3.21. Q. Core dump on SGI when using the gl module.  There are conflicts between entry points in the termcap and curses  libraries and an entry point in the GL library.  There's a hack of a | 
