[asterisk-bugs] [Asterisk 0013557]: [patch] Asterisk won't compile against uclibc

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13557 
====================================================================== 
Reported By:                nickpeirson
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13557
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 144419 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-25 10:34 CDT
Last Modified:              2008-10-08 23:40 CDT
====================================================================== 
Summary:                    [patch] Asterisk won't compile against uclibc
Description: 
index is used in main/pbx.c. This breaks compilation under uclibc as it
doesn't provide the index function. Replacing this with strchr, which index
is an alias for, solves the problem.
====================================================================== 

---------------------------------------------------------------------- 
 (0093399) murf (administrator) - 2008-10-08 23:40
 http://bugs.digium.com/view.php?id=13557#c93399 
---------------------------------------------------------------------- 
THings left to do:

1. get the rest of the bcopy,bzero occurrences in the source:
 ./channels/console_video.c
 ./channels/console_gui.c
 ./channels/vcodecs.c
 ./main/rtp.c
 ./main/cli.c
 ./channels/chan_usbradio.c
 ./channels/chan_iax2.c
2. bcopy and bzero will creep back into the source-- we need
   to:
     a. Make a note in the GUIDELINES
     b. put a macro for them that will generate an error into asterisk.h
        or some other worthy header file.
3. If they are expunged from the source, then they can be removed from
   the configure script (and the .ac, etc). Why check for something
   that won't be used?

nickpeirson-- don't worry about these items, I've already done them,
they weren't that much work. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-08 23:40 murf           Note Added: 0093399                          
======================================================================