Bugs item #1450019, was opened at 2006-03-14 16:23 Message generated for change (Comment added) made by nnorwitz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1450019&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: Python 2.3 >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Sydney Weidman (weidmans) >Assigned to: Neal Norwitz (nnorwitz) Summary: Build of readline fails Initial Comment: I was attempting to compile Python-2.3.5 under Fedora Core 4: Python 2.3.5 (#14, Mar 14 2006, 17:57:17) [GCC 4.0.2 20051125 (Red Hat 4.0.2-8)] on linux2 and needed it to have readline support No matter how I compiled it, the readline module was never built, and of course readline functionality did not work. I tried ./configure --with-readline=/usr and a couple of other configure options that I thought would help, but nothing worked. Finally, I tried: make Modules/readline which gave the error: gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -I./Include -L/home/sweidman/Applications/Python-2.3.5 Modules/readline.c -o Modules/readline Modules/readline.c:96: error: static declaration of âhistory_lengthâ follows non-static declaration /usr/include/readline/history.h:242: error: previous declaration of âhistory_lengthâ was here make: *** [Modules/readline] Error 1 So without knowing what I was really doing, I commented out the definition of history_length at Modules/readline.c:96 After making that change, Python-2.3.5 compiled and ran fine with readline support working; i.e. "import readline" gave no errors and the arrow keys bring back the last command. So is this a bug or a quirk on my platform or something else I'm doing wrong? Thanks for the great software!! ---------------------------------------------------------------------- >Comment By: Neal Norwitz (nnorwitz) Date: 2006-03-15 00:08 Message: Logged In: YES user_id=33168 Python 2.3 isn't supported any longer. In the current version, it looks like history_length was renamed to prepend an underscore (ie, the name became: _history_length). This was presumably to fix the same problem. The name also changed in write_history_file(), set_history_length(), and get_history_length(). It's not so much anything you are doing wrong, just a compatability problem, since FC4 is quite a bit newer than Python 2.3. If you upgrade to Python 2.4, you shouldn't have the problem, or you can run with your local modification. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1450019&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
