>Number:         5422
>Category:       pkg
>Synopsis:       python pkg: cryptmodule doesn't work
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May  8 05:05:01 1998
>Last-Modified:
>Originator:     Jaromir Dolecek
>Organization:
	ICS MU, Brno, Czech Republic
>Release:        1.3.1
>Environment:
	
System: NetBSD saruman.ics.muni.cz 1.3.1 NetBSD 1.3.1 (SARUMAN) #0: Sun Apr 19 16:15:24 MEST 1998 dolecek@saruman.ics.muni.cz:/usr/home/dolecek/N131/usr/src/sys/arch/i386/compile/SARUMAN i386


>Description:
	Python (or cryptmodule.so when dynamic loading is used)
	needs to be linked with libcrypt (in order for module crypt
	to work), but it isn't due to a bug in configuration file
	files/Setup.

>How-To-Repeat:
	> python
	Python 1.5.1 (#2, May  8 1998, 13:00:55)  [GCC 2.7.2.2+myc1] on netbsd1
	>>> import test.test_crypt
	/usr/libexec/ld.so: Undefined symbol "_crypt" called from python:./Modules/cryptmodule.so at 0x400e007c

>Fix:
--- files/Setup.orig	Fri May  8 12:50:58 1998
+++ files/Setup	Fri May  8 12:51:08 1998
@@ -146,7 +146,7 @@
 
 # The crypt module is now disabled by default because it breaks builds
 # on many systems (where -lcrypt is needed), e.g. Linux (I believe).
-crypt cryptmodule.c # -lcrypt	# crypt(3); needs -lcrypt on some systems
+crypt cryptmodule.c -lcrypt	# crypt(3); needs -lcrypt on some systems
 
 
 # Some more UNIX dependent modules -- off by default, since these
>Audit-Trail:
>Unformatted: