[asterisk-bugs] [Asterisk 0014264]: compilation warning for main/editline/history

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Jan 20 16:28:36 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14264 
====================================================================== 
Reported By:                dimas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14264
Category:                   General
Reproducibility:            have not tried
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 168729 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-17 06:07 CST
Last Modified:              2009-01-20 16:28 CST
====================================================================== 
Summary:                    compilation warning for main/editline/history
Description: 
While building Asterisk I noticed:

history.c: In function 'history_def_add':
history.c:352: warning: implicit declaration of function 'strlcpy'
history.c:353: warning: implicit declaration of function 'strlcat'
   [CC] hash/hash.c -> hash/hash.o

I'm not sure if it affects anything but not having warnings during
compilation is definitely the Good Thing.
====================================================================== 

---------------------------------------------------------------------- 
 (0098266) putnopvut (administrator) - 2009-01-20 16:28
 http://bugs.digium.com/view.php?id=14264#c98266 
---------------------------------------------------------------------- 
An alternate route would be to not use these functions if HAVE_STRLCPY and
HAVE_STRLCAT are not defined and instead use strncpy and strncat. You'd
just have to subtract 1 from the size argument to guarantee that a null
byte is written to the end of the string. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-20 16:28 putnopvut      Note Added: 0098266                          
======================================================================




More information about the asterisk-bugs mailing list