Am 13.12.11 16:58, schrieb Jürgen Schmidt:
On 12/13/11 4:10 PM, Raphael Bircher wrote:
Hi at all

I was running in a build breaker in ucpp

=============
Building module ucpp
=============

Entering /Users/server3/Documents/build34/main/ucpp

mkdir: ./unxmacxi.pro/misc/build/ucpp/: File exists
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/assert.c
assert.c: In function 'ucpp_handle_assert':
assert.c:181: warning: 't.line' is used uninitialized in this function
assert.c:134: warning: 'aname' may be used uninitialized in this function assert.c:131: warning: 't.name' may be used uninitialized in this function
assert.c:133: warning: 'a' may be used uninitialized in this function
assert.c: In function 'ucpp_handle_unassert':
assert.c:295: warning: 't.line' is used uninitialized in this function
assert.c:245: warning: 't.name' may be used uninitialized in this function
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/cpp.c
cpp.c: In function 'handle_if':
cpp.c:1049: warning: 'rt.line' is used uninitialized in this function
cpp.c:1126: warning: 'rt.line' is used uninitialized in this function
cpp.c:1167: warning: 'rt.line' is used uninitialized in this function
cpp.c:995: warning: 't.name' may be used uninitialized in this function
cpp.c:987: warning: 'tf.t' may be used uninitialized in this function
cpp.c: In function 'handle_include':
cpp.c:1200: warning: 'fname' may be used uninitialized in this function
cpp.c:1275: warning: 't.name' may be used uninitialized in this function
cpp.c:1299: warning: 't.name' may be used uninitialized in this function
cpp.c: In function 'handle_line':
cpp.c:1451: warning: 't.name' may be used uninitialized in this function
cpp.c: In function 'handle_cpp':
cpp.c:1646: warning: 't.line' is used uninitialized in this function
cpp.c:1641: warning: 't.name' may be used uninitialized in this function
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/eval.c
eval.c: In function 'pp_strtoconst':
eval.c:306: warning: 'rs' may be used uninitialized in this function
eval.c: In function 'eval_shrd':
eval.c:407: warning: 'r.sign' may be used uninitialized in this function
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/hash.c
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/lexer.c
lexer.c: In function 'ucpp_next_token':
lexer.c:798: warning: 'shift_state' may be used uninitialized in this
function
lexer.c:799: warning: 'utf8' may be used uninitialized in this function
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/macro.c
macro.c: In function 'ucpp_substitute_macro':
macro.c:1031: warning: 'atl' may be used uninitialized in this function
macro.c:760: warning: 't.name' may be used uninitialized in this function
macro.c:935: warning: 'd' may be used uninitialized in this function
macro.c:1034: warning: 'save_tfi' may be used uninitialized in this
function
macro.c: In function 'ucpp_handle_define':
macro.c:493: warning: 't.name' may be used uninitialized in this function
macro.c:322: warning: 'mv.t' may be used uninitialized in this function
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/mem.c
Compiling: ucpp/unxmacxi.pro/misc/build/ucpp/nhash.c
nhash.c: In function 'find_node':
nhash.c:137: warning: 'ls' may be used uninitialized in this function
nhash.c: In function 'internal_put':
nhash.c:232: warning: 'pnode' may be used uninitialized in this function
Making: ucpp
unx
-rwxr-xr-x 1 server3 staff 96608 Dec 13 16:01
../../../../unxmacxi.pro/bin/ucpp
Making: all_ucpp.dpobj

Any Idea whats wrong

what exactly is your problem? The output shows only warnings which are ok, the original source code is untouched.

I have built and tested ucpp on Linux, MacOS and Windows without any problem. Nevertheless do i currently review/test Ariel's patch. He had problems with strange dependencies to uwinapi or salcprt ...
Ok, the Error is in redland

make[3]: Nothing to be done for `all'.
/bin/sh ../libtool --tag=CC --mode=compile /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I/Users/server3/Documents/build34/main/redland/redland/../unxmacxi.pro/inc -I/Users/server3/Documents/build34/main/solver/340/unxmacxi.pro/inc/external -isysroot /Developer/SDKs/MacOSX10.4u.sdk -I../../../../inc -I../../../../inc -DPKGDATADIR="\"/usr/local/share/redland\"" -I/Users/server3/Documents/build34/main/redland/redland/../unxmacxi.pro/inc -I/Users/server3/Documents/build34/main/solver/340/unxmacxi.pro/inc/external -isysroot /Developer/SDKs/MacOSX10.4u.sdk -I../../../../inc -I../../../../inc -DLIBRDF_INTERNAL=1 -g -O2 -MT rdf_digest_openssl.lo -MD -MP -MF .deps/rdf_digest_openssl.Tpo -c -o rdf_digest_openssl.lo rdf_digest_openssl.c /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I/Users/server3/Documents/build34/main/redland/redland/../unxmacxi.pro/inc -I/Users/server3/Documents/build34/main/solver/340/unxmacxi.pro/inc/external -isysroot /Developer/SDKs/MacOSX10.4u.sdk -I../../../../inc -I../../../../inc -DPKGDATADIR=\"/usr/local/share/redland\" -I/Users/server3/Documents/build34/main/redland/redland/../unxmacxi.pro/inc -I/Users/server3/Documents/build34/main/solver/340/unxmacxi.pro/inc/external -isysroot /Developer/SDKs/MacOSX10.4u.sdk -I../../../../inc -I../../../../inc -DLIBRDF_INTERNAL=1 -g -O2 -MT rdf_digest_openssl.lo -MD -MP -MF .deps/rdf_digest_openssl.Tpo -c rdf_digest_openssl.c -fno-common -DPIC -o .libs/rdf_digest_openssl.o rdf_digest_openssl.c: In function 'librdf_openssl_ripemd160_register_factory': rdf_digest_openssl.c:155: error: 'SHA_DIGEST_LENGTH' undeclared (first use in this function) rdf_digest_openssl.c:155: error: (Each undeclared identifier is reported only once
rdf_digest_openssl.c:155: error: for each function it appears in.)
make[3]: *** [rdf_digest_openssl.lo] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [all-recursive] Error 1
dmake: Error code 2, while making '../unxmacxi.pro/misc/build/so_built_so_redland'

1 module(s):
    redland
need(s) to be rebuilt

Reason(s):

ERROR: error 65280 occurred while making /Users/server3/Documents/build34/main/redland/redland

When you have fixed the errors in that module you can resume the build by running:

    build --all:redland



--
My private Homepage: http://www.raphaelbircher.ch/

Reply via email to