Bug 246 - md5_crypt conflict fails
Summary: md5_crypt conflict fails
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: -current
Hardware: Other Linux
: P2 major
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-17 16:48 AEST by James
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James 2002-05-17 16:48:18 AEST
on both a slackware 7.1 and slackware 8.0 system when attempting
--with-md5-passwords everything is fine except one line of configure:
checking for md5_crypt... no

checking config.log yields:
  $ ./configure --with-md5-passwords --with-bsd-auth --sysconfdir=/etc/ssh
--with-ipv4-default
configure:6441: checking for md5_crypt
openssh-3.2.2p1/configure:6474: undefined reference to `md5_crypt'
    which can conflict with char md5_crypt (); below.  */
char md5_crypt ();
#if defined (__stub_md5_crypt) || defined (__stub___md5_crypt)
f = md5_crypt;
ac_cv_func_md5_crypt=no

fought w/ this an hour, played w/ editing the configure, played w/ compiling new
openssl, any help would be welcome
Comment 1 Tim Rice 2002-05-18 03:12:30 AEST
Perhaps you are getting confused by the "MD5 password support: no" line.
configure is reporting that in error as pointed out by 
Kagan Kongar <kongar@tsrsb.org.tr>
Try removing line 2026 (MD5_MSG="no") of configure.ac and run autoconf.
If you don't have autoconf 2.52, grab the corrected configure from
http://www.multitalents.net/openssh/configure-OpenSSH_3.2.2p1.gz or
ftp://ftp.multitalents.net/pub/openssh/configure-OpenSSH_3.2.2p1.gz
Comment 2 Kevin Steves 2002-07-18 15:42:43 AEST
tim, should this be closed INVALID?
Comment 3 Tim Rice 2002-07-19 02:42:34 AEST
No resonse from quelrods@mail.utexas.edu (James) in 2 months,
I'm marking it INVALID and closing.
Reopen if it's still a problem in the current code.
Comment 4 Damien Miller 2004-04-14 12:24:18 AEST
Mass change of RESOLVED bugs to CLOSED