BlogJava-miaoyachun-随笔分类-C

solution for axis2c-src-1.6.0 build failure on 64 bit ubuntu14.04s

Milo的海域 — Fri, 21 Aug 2015 03:00:00 GMT

Two compile issues i got:

One issue is:

uuid_gen_unix.c: In function 'axutil_uuid_gen_v1':uuid_gen_unix.c:62:20: error: variable 'tv' set but not used [-Werror=unused-but-set-variable] struct timeval tv; ^cc1: all warnings being treated as errors

Solution is remove "-Werror" in all configure scripts

find -type f -name configure -exec sed -i '/CFLAGS/s/-Werror//g' {} \;

Another issue is:

/usr/bin/ld: test.o: undefined reference to symbol 'axiom_xml_reader_free'
/usr/local/axis2c/lib/libaxis2_parser.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[4]: *** [test] Error 1
make[4]: Leaving directory `/home/miaoyachun/softwares/test/axis2c-src-1.6.0/neethi/test'

As suggested in https://code.google.com/p/staff/issues/detail?id=198, the solution is disable neethi/test in following files:

neethi/configure, remove all "test/Makefile"
neethi/Makefile.am, update "SUBDIRS = src test" with "SUBDIRS = src"
neethi/Makefile.in, update "SUBDIRS = src test" with "SUBDIRS = src"

Finally, you could run "make; sudo make install"" successfully. Last thing should be paid attention to is you may need copy all head files of neethi/include into /usr/local/axis2c/include/axis2-1.6.0/ which needed when you compile customized web service.

Enjoining it!!

Milo的海域 2015-08-21 11:00 发表评论

axis2/c的hello.c编译不过的原因

Milo的海域 — Tue, 18 Aug 2015 09:59:00 GMT

http://axis.apache.org/axis2/c/core/docs/axis2c_manual.html#client_api 的hello.c client 编译命令在我的ubuntu 12.04s上总是报错

gcc -o hello -I$AXIS2C_HOME/include/axis2-1.6.0/ -L$AXIS2C_HOME/lib -laxutil -laxis2_axiom -laxis2_parser -laxis2_engine -lpthread -laxis2_http_sender -laxis2_http_receiver -ldl -Wl,--rpath -Wl,$AXIS2C_HOME/lib hello.c
/tmp/ccCYikFh.o: In function `main':
hello.c:(.text+0x57): undefined reference to `axutil_env_create_all'
hello.c:(.text+0x68): undefined reference to `axis2_options_create'
hello.c:(.text+0x93): undefined reference to `axutil_strcmp'
hello.c:(.text+0xeb): undefined reference to `axis2_endpoint_ref_create'
hello.c:(.text+0x102): undefined reference to `axis2_options_set_to'
hello.c:(.text+0x13d): undefined reference to `axis2_svc_client_create'
hello.c:(.text+0x168): undefined reference to `axutil_error_get_message'
hello.c:(.text+0x193): undefined reference to `axutil_log_impl_log_error'
hello.c:(.text+0x1b1): undefined reference to `axis2_svc_client_set_options'
hello.c:(.text+0x1d6): undefined reference to `axis2_svc_client_send_receive'
hello.c:(.text+0x21d): undefined reference to `axiom_node_free_tree'
hello.c:(.text+0x238): undefined reference to `axutil_error_get_message'
hello.c:(.text+0x266): undefined reference to `axutil_log_impl_log_error'
hello.c:(.text+0x28d): undefined reference to `axis2_svc_client_free'
hello.c:(.text+0x2a8): undefined reference to `axutil_env_free'
/tmp/ccCYikFh.o: In function `build_om_request':
hello.c:(.text+0x2ed): undefined reference to `axiom_element_create'
hello.c:(.text+0x307): undefined reference to `axiom_element_set_text'
/tmp/ccCYikFh.o: In function `process_om_response':
hello.c:(.text+0x337): undefined reference to `axiom_node_get_first_child'
hello.c:(.text+0x351): undefined reference to `axiom_node_get_node_type'
hello.c:(.text+0x367): undefined reference to `axiom_node_get_data_element'
hello.c:(.text+0x381): undefined reference to `axiom_text_get_value'
hello.c:(.text+0x396): undefined reference to `axiom_text_get_value'
collect2: error: ld returned 1 exit status

仔细检查了gcc命令，头文件，库文件的路径都是对的，最后跟同事讨论才发现hello.c的位置的问题。。如果hello.c的位置放到了依赖库的右面就会报类似错误。但是官方的例子应该是测试过的，怎么会有这个问题呢? 难道我的ubuntu 12.04的gcc比较严格？

修正后的gcc命令如下

gcc -o hello hello.c -I$AXIS2C_HOME/include/axis2-1.6.0/ -L$AXIS2C_HOME/lib -laxutil -laxis2_axiom -laxis2_parser -laxis2_engine -lpthread -laxis2_http_sender -laxis2_http_receiver -ldl -Wl,--rpath -Wl,$AXIS2C_HOME/lib

Milo的海域 2015-08-18 17:59 发表评论

valgrind memory check on java program

Milo的海域 — Fri, 06 Dec 2013 02:26:00 GMT

Java程序的memory leak分析也可以用valgrind, 尤其是JNI程序尤其有用:

valgrind --error-limit=no --trace-children=yes --smc-check=all --leak-check=full JAVA_CMD

特意写了个有leak的jni函数，用valgrind成功检查出来了

==31915== 100 bytes in 1 blocks are definitely lost in loss record 447 of 653
==31915== at 0x402CE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==31915== by 0x60424F9: Java_MyJNI_hello (MyJNI.c:16)

在老版本valgrind(3.5.0) enable了--trace-children选项后可能出现错误:

 Error occurred during initialization of VM    
 Unknown x64 processor: SSE2 not supported

升级到最新版可以解决这个问题，升级方法：下载src包解压后执行 ./configure; make; make install

Milo的海域 2013-12-06 10:26 发表评论

htonll & ntohll in C

Milo的海域 — Tue, 23 Jul 2013 08:42:00 GMT

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <arpa/inet.h>
#include <inttypes.h>

uint64_t htonll(uint64_t val) {
    return (((uint64_t) htonl(val)) << 32) + htonl(val >> 32);
}

uint64_t ntohll(uint64_t val) {
    return (((uint64_t) ntohl(val)) << 32) + ntohl(val >> 32);
}
int main() {
    uint64_t hll = 0x1122334455667788;
    printf("uint64: %"PRIu64"\n", hll);
    printf("0x%"PRIX64"\n", hll);
    printf("htonll(hll) = 0x%"PRIX64"\n", htonll(hll));
    printf("ntohll(htonll(hll)) = 0x%"PRIX64"\n", ntohll(htonll(hll)));
    printf("ntohll(hll) = 0x%"PRIX64"\n", ntohll(hll)); // no change
    return 1;
}

big endian(network byte order), little endian (host byte order in intel arch)

Milo的海域 2013-07-23 16:42 发表评论