According to Jeroen: While burning my CPU.
> 
> Hello all
> 
> I keep getting an errormessage no mather what type
> of Linux I try in the Makefile.
> It is allways with smbpass.c
> Message:
>     In file included from smbpass.c:20:
>     includes.h:288: crypt.h: No such file or directory
>     make: ***smbpass.o Error 1
> And indeed there is no file called crypt.h in the sourcefile
> of samba.
> Howcome?
> How do I get this crypt.h file?
> I use Slackware 3.4  kernel 2.0.34.

Well crypt.h is a linux-source header file and resides in
/usr/src/linux/arch/ppc/boot/compressed/

This means 
1) you dont have the linux source code installed, 
2) you have it installed in a directory other then /usr/src/linux and it
cant be found by the samba sorce.
3) no symlink in /usr/src called linux pointing to where the linux-source
actaly is.
4) The Makefile needs to be edited to reflect the paths on your system.

I dont have samba here so i can only guess that the file i say is the
correct file. Now to see if we can get samba to go a little further in its
compile try editing "includes.h" MAKE A BACK UP FIRST, line 288 change;

#include <linux/crypt.h>
to;
#include "crypt.h"

This tells make to look in the "local" source tree for crypt.h.
I have attached crypt.h (its a just few liner) put in in your samba source
directory.

Note:
This is just to see if you get a little futher with the compile, but if you
dont have the linux source in its rightfull place then you will possably
get more errors.

-  cut here -----------------------------------

/* crypt.h (dummy version) -- do not perform encryption
 * Hardly worth copyrighting :-)
 */

#ifdef CRYPT
#  undef CRYPT      /* dummy version */
#endif

#define RAND_HEAD_LEN  12  /* length of encryption random header */

#define zencode
#define zdecode

-  cut here ------------------------------------

> What is that PAM in the Makefile

I dont have a samba Makefile here, but its possably regarding PAM
authentication.
pam (securetty shadow passwording). 

> 
> Greetings,
>         Jeroen
> 


-- 
Regards Richard.
[EMAIL PROTECTED]

Reply via email to