On Tue, Dec 12, 2000 at 04:38:36PM -0500, Lisa Thalheim wrote: > > I had problems using the Net::RawIP-perl module with libpcap v0.5 (on a > redhat 6.0-system). > In some files someone used functions called "strlcpy" and "snprint", > which generated errors with the perl DynaLoader: > > > : Can't load > : '/usr/lib/perl5/site_perl/5.005/i386-linux/auto/Net/RawIP/RawIP.so' for > : module > : Net::RawIP: /usr/lib/perl5/site_perl/5.005/i386-linux/auto/Net/RawIP/RawIP.so: >undefined > : symbol: strlcpy at /usr/lib/perl5/5.00503/i386-linux/DynaLoader.pm line > : 169. > > Since the functions seemed odd to me and the UNIX C manpages said they > didn't exist I replaced them by "snprintf" and "strcpy" (or > "strncpy") which made the DynaLoader work. > Somebody who knows C might want to look over the strcpy- and strncpy-calls > since I don't know whether I used the right one in every case. > > I changed the following files: > > gencode.c > inet.c > pcap-dlpi.c > pcap-linux.c > pcap-nit.c > pcap-null.c > pcap-snit.c > > Was this a bug or a feature? (Questions such as this shouldn't be sent to "[EMAIL PROTECTED]", they should be sent to "[EMAIL PROTECTED]".) There are no calls to "strlcpy()" or "snprint()" in the official libpcap 0.5 source on the tcpdump.org Web site - there aren't even any calls to "snprintf()". Where did you get the source code that you modified? Did it really call "snprint()" rather than "snprintf()"? If so, I'd suggest you complain to whoever put those calls into the source. There *are* calls to "strlcpy()" and "snprintf()" (with an "f" at the end) in the current CVS tree for libpcap; however, the configure script checks the C library and, if it doesn't find those routines, it supplies its own routines. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
