It appears my problem was my include files were not really were they
were.
About a month ago, I copied the /usr/include directory to another
partition and placed a symbolic link from /usr/include --> new location
it seems this would have been fine but some of the /usr/include also
had a symbolic link to "../" and since they weren't in /usr anymore the
../ sent it into the wrong directory.
Once I recopied the files back to /usr/include, samba compiled without
errors.
Thank you to all who replied.......
Original Post.
Has anyone successfully compiled (samba-1.9.16p11) under
DU 3.2c WITH enhanced security enabled.
I uncommented the section re: OSF/1 v 2.0 with Enhanced. When I
enter "make" I get the following messages:
/usr/lib/cmplrs/cc/cfe: Error: ./includes.h: 160: Cannot open file
sys/param.h f
or #include
/usr/lib/cmplrs/cc/cfe: Error: /usr/include/grp.h: 49: Cannot open file
sys/type
s.h for #include
for all programs to be compiled.
Does it make a difference where the programs are when I'm compiling them?
or for that matter, where I'm at when compiling them?
I left the default setting for where I want the compiled programs but
currently I have the source in a directory "/drive2/source/samba/source"
I entered "make" from the .../source directory. I chmod 777 to all files
in
case it was a permissions problem, and I've tried compiling both as a
normal and superuser.
Thanx
George Gallen
ggallen_at_slackinc.com
Received on Wed Apr 23 1997 - 18:36:52 NZST