"Chakravarthula, Krishnamurthy" <[EMAIL PROTECTED]> writes:
> configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
> configure.in: You should verify that configure.in invokes
> AM_INIT_AUTOMAKE,
> configure.in: that aclocal.m4 is present in the top-level directory,
> configure.in: and
Hi Jostein,
Following are my settings
$ uname -a
SunOS pnsun029 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-V240
$ make --version
automake (GNU automake) 1.10
Written by Tom Tromey <[EMAIL PROTECTED]>
and Alexandre Duret-Lutz <[EMAIL PROTECTED]>.
Copyright 2006 Free Software Fou
Dale King wrote:
MDC::put( "key", "value1" );
MDC::put( "key", "value2" );
Without a code example, I must ask; are these MDC::put calls in the same thread
right next to each other?
The attached program correctly swaps keys in 0.9.7. I don't have an installed
0.10.0 build handy at the
"Chakravarthula, Krishnamurthy" <[EMAIL PROTECTED]> writes:
> $ uname -a
> SunOS pnsun029 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-V240
>
> $ make --version
> automake (GNU automake) 1.10
> Written by Tom Tromey <[EMAIL PROTECTED]>
>and Alexandre Duret-Lutz <[EMAIL PROTECTED]>.
>
>
On Apr 16, 2008, at 10:33 AM, Jacob L. Anawalt wrote:
Dale King wrote:
MDC::put( "key", "value1" );
MDC::put( "key", "value2" );
Without a code example, I must ask; are these MDC::put calls in the
same thread right next to each other?
The attached program correctly swaps keys in 0.9.
Curt Arnold wrote:
".. insertion takes place only if there is not already an element in the
m (map) with that key."
Right. I usually take the easy way (less lines of code) out with the operator[]
override unless I need to know that the key existed before inserting a new one
or replacing i
I just noticed that Mr. Chakravarthula is referring to 1.2.2 of apr and
apr-util.
But Mr. Tveit says to use 1.2.12, which I think is correct.
Could this be the problem?
I also notice that the "INSTALL" file that comes in the .zip download
includes the following:
---
The following files pla
They were in the same thread . In reality it was a loop in a demo program to
demonstrate log4cxx to people where I work so that we switch to it. In
reality there was only statement that get executed each time through the
loop with different data. In my testing the data in the MDC got stuck at the
f
Since it appears what you really are having is a APR build problem,
you might have a wider pool of Solaris users on apr-user that might
recognize your roblem.
You do not mention what version of Solaris (8, 9, 10, Sun or
OpenSolaris) you are using and what processor (SPARC, x86 or x86-64).
