axis2/c does not build on Mac OS X
----------------------------------

                 Key: AXIS2C-1540
                 URL: https://issues.apache.org/jira/browse/AXIS2C-1540
             Project: Axis2-C
          Issue Type: Bug
          Components: core/transport, util
    Affects Versions: 1.6.0
         Environment: Mac OS X
            Reporter: Halewijn Geerts


1) dir_handler.c : struct dirent * should not be const on mac

  extern int AXIS2_ALPHASORT(
      );
  #ifdef IS_MACOSX
  int dir_select(
      struct dirent *entry);
  int file_select(
<    const struct dirent *entry);
>    struct dirent *entry); //removed const to make it build on mac
  #else
  int dir_select(
      const struct dirent *entry);
  int file_select(
      const struct dirent *entry); 
  #endif



< int
< file_select(
<     const struct dirent *entry)
< {
< 
<       #ifdef IS_MACOSX
<               int     file_select(struct dirent *entry);
<       #else
<               int file_select(const struct dirent *entry);
<       #endif 

> #ifdef IS_MACOSX
> int   
> file_select( struct dirent *entry ); //removed const to make it build on mac
> #else
> int 
> file_select( const struct dirent *entry );
> #endif
> {

2) axutil_unix.h : conflicting declaration of usleep

   #ifdef HAVE_UNISTD_H
   #include <unistd.h>
< extern int usleep (__useconds_t __useconds);
   #endif                          /*HAVE_UNISTD_H */

3) axis2_libcurl.c : missing initialization of variable in axis2_libcurl_send

   unsigned int buffer_size = 0;
   int content_length = -1;
< axis2_char_t *content_type;
> axis2_char_t *content_type = NULL;
   axis2_char_t *content_len = AXIS2_HTTP_HEADER_CONTENT_LENGTH_;
   const axis2_char_t *char_set_enc = NULL;
  axis2_char_t *content = AXIS2_HTTP_HEADER_CONTENT_TYPE_;



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to