ports/129439: devel/libusb does not compile in FreeBSD 7.0-RELEASE

[Volker Jahns]

The following reply was made to PR ports/129439; it has been noted by GNATS.

From: Volker Jahns <volker at thalreit.de>
To: Rene Ladan <r.c.ladan at gmail.com>
Cc: bug-followup at freebsd.org
Subject: Re: ports/129439: devel/libusb does not compile in FreeBSD 7.0-RELEASE
Date: Sun, 07 Dec 2008 10:33:23 +0100

 Rene Ladan schrieb:
 > It builds fine for me on 7.0R/i386, 7.0R/amd64 and 7.1/amd64.
 > There are no error reports on http://portsmon.freebsd.org/portserrs.py
 >
 > Is there anything non-standard in your environment setings or /etc/make.conf ?
 > Which compiler version do you use?
 >   
 Yes, on 6.2-STABLE I do not observe this problem either.
 
 On 7.0-RELEASE libusb won't compile.
 
 The information you requested
 --
 volker at caspar ~ > gcc -dumpversion
 4.2.1
 volker at caspar ~ > gcc -dumpmachine
 i386-undermydesk-freebsd
 
 volker at caspar ~ > cat /etc/make.conf
 # added by use.perl 2008-05-28 18:27:44
 PERL_VER=5.8.8
 PERL_VERSION=5.8.8
 --
 
 however, what I am really concerned about is this error message
 --
 /usr/include/strings.h:44: warning: 'ffs' declared 'static' but never 
 defined
 /usr/include/strings.h:47: warning: 'fls' declared 'static' but never 
 defined
 /usr/include/string.h:62: warning: 'memcmp' declared 'static' but never 
 defined
 /usr/include/string.h:68: warning: 'memset' declared 'static' but never 
 defined
 /usr/include/string.h:74: warning: 'strchr' declared 'static' but never 
 defined
 /usr/include/string.h:101: warning: 'strrchr' declared 'static' but 
 never defined
 --
 gcc issues here warnings which - because of the makefile configuration - 
 leads to a fullstop in the compilation process. If the corresponding 
 configuration option is removed compilation continues and the libraries 
 created are functional ( which I have tested with a 1-Wire DS9097U USB 
 adapter). Therefore I question the configuration option -Werrors in 
 libusb's makefile.
 
 On the other hand, gcc warnings are observed whenever  source code is 
 compiled which includes the system header files <string.h> and/or 
 <strings.h>. This might be caused by outdated and/or inappropriate 
 system headers. I will look into this.
 
 -- 
 Volker Jahns, volker at thalreit.de