speaking of ant, the ant build failedo my mac:
configure:
[echo] Configuring with has.wchar_t=0
[echo] Configuring with logchar_type=utf-8
build:
[cc] Starting dependency analysis for 144 files.
[cc] 0 files are up to date.
[cc] 144 files to be recompiled from dependency analysis.
[cc] 144 total files to be compiled.
[cc] Starting link
[cc] ld: warning -prebind ignored because MACOSX_DEPLOYMENT_TARGET
environment variable greater or equal to 10.4
[cc] ld: Undefined symbols:
[cc] __Unwind_Resume
[cc] __ZN7log4cxx7helpers13UnicodeHelper10decodeWideERPKwS3_
[cc] __ZN7log4cxx7helpers13UnicodeHelper10encodeWideEjPw
[cc] __ZN7log4cxx7helpers13UnicodeHelper10lengthUTF8Ew
[cc] /usr/bin/libtool: internal link edit command failed
BUILD FAILED
/Users/shaideljo/repos/src/users/shai-sand/logging-log4cxx/build.xml:723:
gcc failed with return code 1
i read somewhere i need to link using g++ instead of gcc but failed to
succesfully do so.
any ideas ?
-----Original Message-----
From: "Curt Arnold" <[EMAIL PROTECTED]>
Sent: Wed, October 11, 2006 3:06 pm
To: "Log4CXX User" <[email protected]>
Subject: Re: Problem with a test program
wchar_t is not sufficiently defined for Mac OS/X to allow
implementation of decodeWide(). That particular unsatisfied link is
the sign that the definition of wchar_t could not be determined.
Same issue occurs on Solaris. The Ant build will tell you to build
using has.wchar_t=0 to suppress all the wchar_t based methods. I
believe that --enable-unicode is the corresponding flag for the
autotools build. CFString is the preferred means to represent
Unicode strings on Mac OS/X, but support for CFString in log4cxx has
not been done.
