axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Rose (JIRA)" <>
Subject [jira] Commented: (AXIS2C-737) Unable to build Axis2/C on Linux RHEL3
Date Tue, 30 Oct 2007 13:29:07 GMT


Chris Rose commented on AXIS2C-737:

That allows me to build it successfully, as noted above.

However, I'm not sure how to _test_ that the build is valid at that point.

> Unable to build Axis2/C on Linux RHEL3
> --------------------------------------
>                 Key: AXIS2C-737
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: build system (Unix/Linux)
>    Affects Versions: 1.1.0
>         Environment: Linux matisse 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 13 17:56:20 EDT
2006 i686 i686 i386 GNU/Linux
> gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-56)
> ./configure  --enable-guththila=yes --enable-libxml2=no
>            Reporter: Chris Rose
> Build eventually fails at this point:
>  gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include -I../../../src/core/description
-I../../../src/core/engine -I../../../src/core/phaseresolver -I../../../src/core/deployment
-I../../../src/core/util -I../../../axiom/include -I../../../neethi/include -I../../../util/include
-g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall -Werror -Wno-implicit-function-declaration -g -DAXIS2_SVR_MULTI_THREADED
-MT conf_builder.lo -MD -MP -MF .deps/conf_builder.Tpo -c conf_builder.c  -fPIC -DPIC -o .libs/conf_builder.o
> cc1: warnings being treated as errors
> conf_builder.c: In function `axis2_conf_builder_process_transport_senders':
> conf_builder.c:669: warning: `transport_enum' might be used uninitialized in this function
> make[4]: *** [conf_builder.lo] Error 1
> make[4]: Leaving directory `/home/rosec/modules/pkg_tree/pkg_src/axis2c-1.1.0/obj.i686-redhat-linux-es3/axis2c-src-1.1.0/src/core/deployment'
> Patching configure to remove -Werror from the CFLAGS in the base configure script allows
the build to succeed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message