axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nandika Jayawardana (JIRA)" <>
Subject [jira] [Comment Edited] (AXIS2C-1524) Build failure when enabling curl support
Date Thu, 27 Dec 2012 09:04:14 GMT


Nandika Jayawardana edited comment on AXIS2C-1524 at 12/27/12 9:03 AM:

adjusted and committed the patch to the current svn trunk. Thanks for the patch.
      was (Author: nandika):
    adjusted and commited the patch to the current svn trunk. Thanks for the patch.
> Build failure when enabling curl support
> ----------------------------------------
>                 Key: AXIS2C-1524
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: transport/http
>    Affects Versions: Current (Nightly)
>         Environment: Debian Lenny,  gcc 4.3.2.  SVN trunk checkout rev 1056550
>            Reporter: Bill Blough
>            Assignee: Nandika Jayawardana
>            Priority: Minor
>         Attachments: AXIS2C-1524_patch.diff
> Building with --enable-libcurl fails with the following errors (warnings really, but
-Werror is enabled):
> http_sender.c:3183: error: 'axis2_http_sender_connection_map_create' defined but not
> http_sender.c:3288: error: 'axis2_http_sender_connection_map_get' defined but not used
> Both functions are used in axis2_http_sender_send, which is only defined when not using
> adding #ifndef statements for those two functions produces one more "defined but not
used" warning about axis2_http_sender_connection_map_free.
> In addition to those issues, there is also 
> libcurl/axis2_libcurl.c:121: error: unused variable 'content_len'
> which appears to be caused by code that exists but is commented out.
> I have added the #ifndefs as necessary, and also commented out content_len.
> Also, I have included the error buffer change from Robert Schweikert's patch for AXIS2C-1522.
> At present, I get a clean compile with those changes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message