On Jan 8, 2007, at 5:52 PM, Bob Rossi wrote:
On Mon, Jan 08, 2007 at 05:40:23PM -0600, Curt Arnold wrote:
I'm still unable to get past unresolved references when linking
shared libraries using MinGW. The same problem appears occurs with
either MinGW with a 4.1.1 gcc or a stock gcc. I've attached a
description and instructions to reproduce the problem as part of the
MinGW build bug (https://issues.apache.org/jira/browse/LOGCXX-74). I
would appreciate anyone else interested in a MinGW build
(particularly Bob Rossi) could check that you see the same problems
on your installation and offer any fixes. If can't come up with one
here, will see if the MinGW mailing list might be able to spot the
problem.
I'm using autotools, are you? Did you get past the expat problems by
using expat 2.0.0 and --with-expat?
I was able to build with autotools, but am only getting static
libraries. I was hoping that I could get a working shared library
from autotools to see what I could do to get the Ant build working
with MinGW. However, the autotools build appears to be only
creating static libraries, I'm finding no DLL's or .so's after the
make only .a's and .la'.s.
Is your expat static?
$ ls expat/expat-2.0.0/lib/
libexpat.a libexpat.la
APR does not reference Expat, only APR-util. The same link problems
that occur with log4cxx occur when trying to build APR by itself, so
I was trying to get feedback if you were or were not getting the same
link problems when doing precisely the same build commands that the
Ant build does.
Is your apr static? Are you using apr-1.3.0 from trunk?
$ ls apr/apr-1.3.0-cvs/lib/
apr.exp libapr-1.a libapr-1.la pkgconfig
I am using the APR from trunk. I am having failures building a
shared APR.
Is your apr-util static? Are you using apr-util from svn trunk from
December 14th or later?
$ ls apr-util/apr-util-2006-12-14-cvs/lib/
aprutil.exp libaprutil-1.a libaprutil-1.la pkgconfig
Is your log4cxx static? Is it from svn trunk on or after December
30th?
$ ls logging-log4cxx/logging-log4cxx-2006-12-30-cvs/lib/
liblog4cxx.a liblog4cxx.la
The same problem occurs when building APR or log4cxx as a shared
library. Since APR itself is less complicated, I am trying to get
past the problem with just APR before trying to attack any larger
issues.
I think you are using the ant build, and not the autotools build from
the information you posted. I would attempt to use the autotools
version and let me know if that works for you.
That should have been explicit in the bug report. I did not repeat
all the information in the bug report in the request for feedback
since I referenced the bug report.
autotools is successful in running the unit tests by is only creating
static libraries, no shared libraries.
Could you tell me:
a) if you are successfully creating a log4cxx.dll with the autotools
build.
b) if you get the same link errors I reported when you do the recipe
described in the bug report.
