You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by John Moyer <jm...@telepath.com> on 1999/09/09 16:45:45 UTC
other/4986: unresolved reference to crypt when configuring with apaci
>Number: 4986
>Category: other
>Synopsis: unresolved reference to crypt when configuring with apaci
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Thu Sep 9 07:50:00 PDT 1999
>Last-Modified:
>Originator: jmcomm@telepath.com
>Organization:
apache
>Release: 1.3.9
>Environment:
Caldera Open Linux 2.2 with patches from Calder ftp server available 7 Seo 1999
[root@s223 apache]# uname -a
Linux s223.firmware.com 2.2.5 #1 Fri Jun 4 13:21:02 CEST 1999 i586 unknown
>Description:
After building with the automatic configuration, there was an unresolved
linker reference to crypt. There was no libcrypt installed. I got libcrypt
from
http://www-stat.uni-klu.ac.at/RPMS/uni-klu-suse_5.x/libcrypt1-1.0-5.i386.html
and built it and installed it. Then I added -lcrypt to the extra libraries
macro in two apache Makefiles. Then Apache built and seems to run. I have
not tested the conditional access features of that may use libcrypt.
I hope this helps.
John
>How-To-Repeat:
>Fix:
http://www-stat.uni-klu.ac.at/RPMS/uni-klu-suse_5.x/libcrypt1-1.0-5.i386.html
and -lcrypt in Makefiles
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database automatically because of the potential for mail ]
[loops. If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request from a ]
[developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]