Problems building 2.2.4 on Solaris 7
Hi Just a few minor problems with building Samba 2.2.4: I configure with: CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib -R/usr/local/lib" CC=cc ./configure --with-acl-support --localstatedir=/var/samba --with-configdir=/etc/samba --with-privatedir=/etc/samba --with-quotas --with-automount --with-nisplus-home --with-smbwrapper (I am using Sun's SC5.0 compiler). The configure output included: checking for poptGetContext in -lpopt... yes checking whether to use included popt... no I get this fatal error: Linking shared library bin/smbwrapper.so ld: fatal: library -lpopt: not found ld: fatal: File processing errors. No output written to bin/smbwrapper.so *** Error code 1 make: Fatal error: Command failed for target `bin/smbwrapper.so' The problem is that the rule for bin/smbwrapper.so does not include LDFLAGS: bin/smbwrapper.@SHLIBEXT@: $(PICOBJS) bin/.dummy @echo Linking shared library $@ @$(SHLD) @LDSHFLAGS@ -o $@ $(PICOBJS) $(LIBS) \ @SONAMEFLAG@`basename $@` should be changed to: bin/smbwrapper.@SHLIBEXT@: $(PICOBJS) bin/.dummy @echo Linking shared library $@ @$(SHLD) @LDSHFLAGS@ -o $@ $(PICOBJS) $(LDFLAGS) $(LIBS) \ @SONAMEFLAG@`basename $@` (The rules for bin/smbwrapper.32.@SHLIBEXT@ and bin/winbindd also look wrong because they have a $(LIBS) without a $(LDFLAGS)). Incidently, the rule: bin/pam_smbpass.@SHLIBEXT@: $(PAM_SMBPASS_OBJ) bin/.dummy @echo Linking shared library $@ $(SHLD) @LDSHFLAGS@ -symbolic -o $@ $(PAM_SMBPASS_OBJ) $(LDFLAGS) -lpam $(DYNEXP) $(LIBS) -lc \ @SONAMEFLAG@`basename $@` also looks wrong because the Sun linker does not have a -symbolic option. I also get these warnings: Linking bin/smbpasswd cc: Warning: illegal option -dc cc: Warning: illegal option -dp Linking bin/swat cc: Warning: illegal option -dc cc: Warning: illegal option -dp Linking bin/winbindd cc: Warning: illegal option -dc cc: Warning: illegal option -dp Deleting the line DYNEXP="-dc -dp" from configure.in fixes the problem. Regards Nick
LDFLAGS patch for Samab 2.2.5
Hello I have attached a small patch to fix this problem on Solaris 7: CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib -R/usr/local/lib" CC=cc ./configure --with-acl-support --localstatedir=/var/samba --with-configdir=/etc/samba --with-privatedir=/etc/samba --with-quotas --with-automount --with-nisplus-home --with-smbwrapper ... make ... Linking shared library bin/smbwrapper.so ld: fatal: library -lpopt: not found Nick --- Makefile.in.2.2.5 Sat Jul 6 05:13:26 2002 +++ Makefile.in Sat Jul 6 05:15:37 2002 @@ -631,7 +631,7 @@ bin/smbwrapper.@SHLIBEXT@: $(PICOBJS) bin/.dummy @echo Linking shared library $@ - @$(SHLD) @LDSHFLAGS@ -o $@ $(PICOBJS) $(LIBS) \ + @$(SHLD) @LDSHFLAGS@ -o $@ $(PICOBJS) $(LDFLAGS) $(LIBS) \ @SONAMEFLAG@`basename $@` bin/smbwrapper.32.@SHLIBEXT@: $(PICOBJS32) bin/.dummy
Re: Problem with latest Samba 2.2.7a PGP signed files
Herb Lewis wrote: > > This renaming was to work around a browser problem where browsers > would think any file with a .gz anywhere in the path was a > gzipped file. > Actually, I think it was a web server or transparent cache bug where the web server would tell the client that any file with a .gz in the name was gzipped. Only clients which believed the web server were affected. Nick
Samba-2.2.8pre2 compiler warnings
Hello I just compiled Samba-2.2.8pre2 on 4 different systems: 1) Solaris 7 + cc: WorkShop Compilers 5.0 98/12/15 C 5.0 2) Solaris 9 + cc: WorkShop Compilers 5.0 98/12/15 C 5.0 3) Solaris 9 + cc: Forte Developer 7 C 5.4 2002/03/09 4) IRIX 6.5 + MIPSpro Compilers: Version 7.30 It compiled OK on all systems. I only ran it on 2) since the other systems are 'production' systems. It seems to run OK. There were a number of compiler warnings though. Two of the warnings looks like they could be serious: CLITAR == "client/clitar.c", line 688: warning: argument #4 is incompatible with prototype: prototype: pointer to uint : "include/proto.h", line 303 argument : pointer to ullong A 64 bit integer being used where a 32 bit integer is expected? smbtar make not work on bigendian machines? smbtar may not work for files over 2GB on little endian machines? IRIX TDBUTIL cc-1164 cc: WARNING File = tdb/tdbutil.c, Line = 46 Argument of type "SIG_ATOMIC_T *" is incompatible with parameter of type "sig_atomic_t *". tdb_set_lock_alarm(&gotalarm); A fuller list of warnings is: On 1) I got the following "rpc_parse/parse_spoolss.c", line 1209: warning: assignment type mismatch: pointer to uchar "=" pointer to char "rpc_parse/parse_spoolss.c", line : warning: assignment type mismatch: pointer to uchar "=" pointer to char "passdb/secrets.c", line 291: warning: argument #2 is incompatible with prototype: prototype: pointer to char : "include/proto.h", line 5018 argument : pointer to const char "lib/util.c", line 62: warning: initializer does not fit or is out of range: -1 "tdb/tdbutil.c", line 46: warning: argument #1 is incompatible with prototype: prototype: pointer to int : "include/../tdb/tdb.h", line 130 argument : pointer to volatile int "smbd/quotas.c", line 404: warning: argument #2 is incompatible with prototype: prototype: pointer to int : "/usr/include/rpc/xdr.h", line 340 argument : pointer to uint "smbd/quotas.c", line 408: warning: argument #2 is incompatible with prototype: prototype: pointer to int : "/usr/include/rpc/xdr.h", line 340 argument : pointer to uint "smbd/quotas.c", line 412: warning: argument #2 is incompatible with prototype: prototype: pointer to int : "/usr/include/rpc/xdr.h", line 340 argument : pointer to uint "client/clitar.c", line 688: warning: argument #4 is incompatible with prototype: prototype: pointer to uint : "include/proto.h", line 303 argument : pointer to ullong Compiling tdb/tdbutil.c with -KPIC "tdb/tdbutil.c", line 46: warning: argument #1 is incompatible with prototype: prototype: pointer to int : "include/../tdb/tdb.h", line 130 argument : pointer to volatile int Compiling nsswitch/winbind_nss.c with -KPIC "nsswitch/winbind_nss.c", line 600: warning: argument #2 is incompatible with prototype: prototype: pointer to int : "nsswitch/winbind_nss.c", line 529 argument : pointer to uint (plus about 20 similar messages in nsswitch/winbind_nss.c). On 2) I get the same warnings as 1). On 3) I get the same as 1) and 2) with the following additions/changes: Compiling passdb/pass_check.c "passdb/pass_check.c", line 669: warning: implicit function declaration: crypt Compiling client/clitar.c "client/clitar.c", line 688: warning: argument #4 is incompatible with prototype: prototype: pointer to unsigned int : "include/proto.h", line 303 argument : pointer to unsigned long long Compiling smbwrapper/smbw.c with -KPIC "smbwrapper/smbw.c", line 1413: warning: implicit function declaration: _fork Compiling smbwrapper/smbw_dir.c with -KPIC "smbwrapper/smbw_dir.c", line 570: warning: implicit function declaration: _getcwd Compiling smbwrapper/wrapped.c with -KPIC "smbwrapper/wrapped.c", line 39: warning: implicit function declaration: smbw_path "smbwrapper/wrapped.c", line 40: warning: implicit function declaration: smbw_open (plus lots of similar messages). On 4) I there are lots of warnings but these are the most interesting ones: Compiling smbd/password.c cc-1164 cc: WARNING File = smbd/password.c, Line = 664 Argument of type "const char *" is incompatible with parameter of type "char \ *" . setnetgrent(group); ^ Compiling smbd/reply.c cc-1552 cc: WARNING File = smbd/reply.c, Line = 2575 The variable "data" is set but never used. char *data; ^ cc-1552 cc: WARNING File = rpc_server/srv_spoolss_nt.c, Line = 335 The variable "i" is set but never used. int i; Compiling rpc_parse/parse_spoolss.c cc-1515 cc: WARNING File = rpc_parse/parse_spoolss.c, Line = 1209 A value of type "char *" cannot be assigned to an entity of type "unsigned char *". r_u->data = prs_alloc_mem(ps, r_u->size); ^ cc-1515 cc: WARNING File = rpc_parse/parse
Samba 2.2.8 acl compatibility documentation error
Hello I think there is a small error in the 'acl compatibility' documentation. In the first sentence in the smb.conf.5.html web page it currently says: New in Samba 2.2.8 and above, this string parameter tells smbd if it should modify any Windows access control lists created from POSIX access control lists to remove features which are not supported by Windows 2000 but not supported by ^^^ ^^^ the Windows NT ACL edit. control. ^ I think it should say: New in Samba 2.2.8 and above, this string parameter tells smbd if it should modify any Windows access control lists created from POSIX access control lists to remove features which are supported by Windows 2000 but not supported by the Windows NT ACL edit control. But I may be wrong - perhaps the 'but' should be an 'or'. Regards Nick
Samba 2.2.8 large file bug in smbwrapper and permissions bug?
Hello Compiling 2.2.8 and smbwrapper on Solaris 9, I saw the following warnings: Compiling smbwrapper/smbw.c with -KPIC "smbwrapper/smbw.c", line 1258: warning: argument #4 is incompatible with prototype: prototype: pointer to ullong : "include/proto.h", line 303 argument : pointer to uint Compiling smbwrapper/smbw_stat.c with -KPIC "smbwrapper/smbw_stat.c", line 149: warning: argument #4 is incompatible with prototype: prototype: pointer to ullong : "include/proto.h", line 303 argument : pointer to uint (Also several less worrying int/uint warnings). These warnings worried me so I tested smbsh listing a large file created using mkfile in a directory which is shared by Samba: $ /usr/sbin/mkfile 5g 5gig $ ls -l 5gig -rw--- 1 nick staff5368709120 Mar 16 11:47 5gig $ smbsh Username: Password: $ cd /smb/ $ ls -l 5gig -rw-r--r-- 1 nick staff1073741824 Mar 16 11:47 5gig *** I also just noticed the differences in permissions - that is more worrying than the large file problem. *** BTW I notice that smbwrapper is not built on the Solaris systems in the bulid farm. Can it be added? Regards Nick
Re: Showstopper! Samba 2.2.8 can't read TDB files from previousversions.
Fredrik Ohrn wrote: It seems that Samba 2.2.8 is unable to open TDB files written by older versions. Instead it just overwrites them with a fresh file. This caused our domain-server to loose the domain SID leaving all our NT clients out in the cold. We use a domain SID extracted from the previous PDC, an old WinNT 4.0 server that was scrapped. Our print server also lost it's registry of printerdrivers and settings. I have not seen any problem on the two Samba PDC's I upgraded (although my test system went from 2.2.7a to 2.2.8 via 2.2.8pre2). I seem to be able to logon as a domain user and access network drives OK. Roaming profiles seem to copy OK. I can use rpcclient to enumerate drivers OK, but I have not really been using Samba for printing because of the printer settings problem on Solaris (hopefully fixed now). I only have Windows 2000 clients. It is probably worth posting more information about your setup. Regards Nick
