Hi Ernst, Problem is that HPUX does not have a C99 compatible version of snprintf (or vsnprintf, I forget which). Either way, what happens is that the snprintf.c module has ifdef's that make sure that we DON'T include stdio.h if we are going to redefine snprintf or vsnprintf (which we ARE, since we don't have a C99 version). The ifdef's do their job, but UNFORTUNATELY, we DO include another module, called stdlib.h, which includes pwd.h, which includes stdio.h (oops!), and so you get the redefinition error. Not actually sure what to do about this at this time.... I'll let you know if I come up with anything... Don
-----Original Message----- From: Ernst Cozijnsen [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 11, 2002 5:38 To: [EMAIL PROTECTED] Subject: is this the right maillist? \Is this the right list for these type of questions?? When i do a configure --with-fhs everything seems 2 go fine but when i do a make i get this: ILE="/usr/local/samba/etc/samba/private/smbpasswd.tdb" Using LIBS = -lgen -lsec -lnsl Compiling lib/snprintf.c lib/snprintf.c:764: conflicting types for `vsnprintf' /opt/gnu/lib/gcc-lib/hppa1.1-hp-hpux/3.0/include/stdio.h:494: previous declaration of `vsnprintf' lib/snprintf.c:779: conflicting types for `snprintf' /opt/gnu/lib/gcc-lib/hppa1.1-hp-hpux/3.0/include/stdio.h:493: previous declaration of `snprintf' make: *** [lib/snprintf.o] Error 1 It seems there are a few differences of declarations in the include files. We use gcc version 3.0 and on the OS we've got the latest patchbundel of June installed. Is this a knows error? and is there a fix for it? With kind regards, Ernst Cozijnsen -- **************************************************************************** This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is only intended for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. ****************************************************************************
