[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    can't build kcheckpass from kde3.1 on rh7.2?  missing crypt funct
From:       "Furnish, Trever G" <TGFurnish () herff-jones ! com>
Date:       2003-02-26 22:41:53
[Download RAW message or body]

Help?  Building kde3.1 using konstruct on redhat 7.2 and having a problem
getting kcheckpass to build.  Specificly, this is the relevant (i think)
portion of the output of the build process.

/bin/sh ../libtool --silent --mode=link cc  -ansi -W -Wall -pedantic
-Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2  -I/mnt/space/kde3.1/include
-I/usr/X11R6/include -L/mnt/space/kde3.1/lib -L/usr/X11R6/lib -O2 -pipe
-D_GNU_SOURCE  -L/mnt/space/kde3.1/lib -L/usr/X11R6/lib -o kcheckpass
kcheckpass.o checkpass_etcpasswd.o checkpass_pam.o checkpass_shadow.o
checkpass_osfc2passwd.o checkpass_aix.o  -L/usr/X11R6/lib
-L/mnt/space/kde3.1/lib  -lkdefakes -lpam -ldl -lresolv 
checkpass_etcpasswd.o: In function `Authenticate':
checkpass_etcpasswd.o(.text+0x26): undefined reference to `crypt'
collect2: ld returned 1 exit status
make[3]: *** [kcheckpass] Error 1
make[3]: Leaving directory
`/root/konstruct/kde/kdebase/work/kdebase-3.1/kcheckpass'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/root/konstruct/kde/kdebase/work/kdebase-3.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/root/konstruct/kde/kdebase/work/kdebase-3.1'
make: *** [build-work/kdebase-3.1/Makefile] Error 2

My C programming skill is pretty weak, but I've tried:
- removing all references to checkpass_etcpasswd* out of the Makefile and
re-making.
- re-running configure after nuking config.status from the kdebase-3.1
directory, adding --with-pam=yes to the configure string I found listed in
config.log.
- ditto, but with with-pam=kde instead.
- defining HAVE_PAM in kcheckpasswd.h and doing all the steps above again.

None helped (although a nice variety of errors was listed :-).  Help?

Oh, I also did a man crypt, discovered that the man page says it's part of
unistd.h, searched for unistd.h on my system, and found that only two of the
ten unistd.h files on the system in various places define a crypt call.  But
I have no idea how to use that info to fix the problem, if it's even
relevant. :-(

Glad to post any additional info anyone thinks may be helpful.

--
Trever
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]