The Samba-Bugzilla – Bug 879
compiling smbd/quotas.c failed
Last modified: 2005-11-14 09:25:25 UTC
redhat 9 i386
./configure --prefix=/usr --localstatedir=/var --with-configdir=/etc/samba
--with-privatedir=/etc/samba --with-fhs --with-quotas --with-smbmount --with-pam
--with-pam_smbpass --with-syslog --with-utmp --enable-cups --with-ldap
--with-ldapsam --with-acl-support --with-sambabook=/usr/share/swat/using_samba
smbd/quotas.c: In function `get_smb_linux_vfs_quota':
smbd/quotas.c:135: storage size of `D' isn't known
make: *** [smbd/quotas.o] Error 1
make: *** Waiting for unfinished jobs....
error: Bad exit status from /var/tmp/rpm-tmp.31652 (%build)
I was able to compile samba-3.0.1pre3 without a problem. I didn't try
samba-3.0.1rc1 because I can't find the SRPM on samba.org servers.
Metze, I remember you saying that this was a header file/glibc problem but the
poster here sounds like he has a pretty simple system. What gives?
can you give me the output of configure
and your /usr/include/linux/quota.h
Tim, I'm working on porting the samba2.2 samba_linux_quota.h to samba3.0
which should clean up all the linux quota mess.
But it's not completely finished yet:-(
/usr/include/linux is a link to /usr/src/linux/include/linux
I'll post the file anyway.
Created attachment 320 [details]
quota.h file from kernel 2.4.20
Version: $Id: quota.h,v 2.0 1996/11/17 16:48:14 mvw Exp mvw $
This is not the quota.h from the 2.4.20 kernel!
and that's what make the trouble...
Can you give me your configure output and source/include/config.h too, please
Created attachment 321 [details]
I ran diff on a fresh kernel 2.4.20 from kernel.org and the one I have and the
two quota files are the exact same.
Created attachment 322 [details]
Created attachment 323 [details]
*** Bug 895 has been marked as a duplicate of this bug. ***
can you try 3.0.2pre1, it should be fixed there
3.0.2pre1 does compile.
I can't close the bug but I guess it can be closed since I can compile.
does it only compile or does it also work correct?
what is when some one is over quota, is the free disk space displayed
Marking as fixed.
In reply to Comment #14
It seems to be working properly. Free space is displayed/updated correctly.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.