Hi somayeh,
This note refers to the old log4cxx hosting site on sourceforge.
http://logging.apache.org/log4cxx
is the correct and current log4cxx
web site.
Best Regards,
Andreas
somayeh bakhshaei wrote:
hi
thanks a lot Mr. Anawalt for your answer.
Bu
Hi,
you seem to have a mixture between log4cxx and log4cpp:
/usr/local/include/log4cpp/Category.hh:624: error:
^
The easiest solution might be to remove the liblog4cpp4/5-dev package.
Or, add "-I/path/to/log4cxx/include" as a compiler option.
A good starting point could
Hi Curt,
I dont currently have much time to work on log4cxx,
but a quick review of the .tar.gz file at least showed that the
UNIX configure script is missing. This results in a dependency
on the GNU autotools to generate the configure script and the Makefile.in's
before building, instead of the st
Hi,
which compiler version are you using (g++ -v)? I remember
that I had the same issue some time ago, but for whatever reason
decided not to track it further down ...
Anyway, can you try to add the following include to socketservertestcase.cpp:
#include
(e.g. on line 54) and report whether it
Hi,
I have just commited a bunch of patches which were already
part of my daily build at http://littletux.homelinux.org/log4cxx/
for some time. With these patches, log4cxx should now be buildable
with much more pedantic warnings enabled, at least with gcc 3.3 it
now builds with
-pedantic-errors -
Hi,
I dont currently have a Windows environment available (can try tomorrow),
but I suspect that your second application is an MFC application,
which seems to use different compiler parameters when compiling
the application than when the log4cxx library was built.
In your second example, have you
Hi Allen,
Conway Allen wrote:
> Hi,
>
>
>
> You used to be able to pick up log4cxx here
> http://littletux.homelinux.org/log4cxx/log4cxx-0.9.8.tar.gz but you
> couldn’t today, and no doubt you haven’t been able to for a while. Where
as Vijai wrote, the correct filename ist
http://littletux.ho
Brian Gore (bgore) wrote:
> I'm trying to download the latest revision of Log4cxx, using the posted
> command:
> svn co http://svn.apache.org/repos/asf/logging/log4cxx/trunk log4cxx
(At least currently), it works here:
$ svn co http://svn.apache.org/repos/asf/logging/log4cxx/trunk log4cxx
A
Hi Andrew,
[EMAIL PROTECTED] wrote:
I am trying to compile svn head on an amd64 machine, but building 32bit
libraries. All I
[...]
funny options. How can I do this? Is there a way to build without ant? Argh!
on UNIX, you can also use the autotools based build system with the usual
./configu
Hi,
anton wrote:
> Hi,
>
> just a small question:
>
> on http://littletux.homelinux.org/log4cxx/
>
> there is mo more windows zip bundle.
> Yes I know that the windows bundle
> is not build automatically, but why
> was the last bundle deleted.
well, this was not intended; it happened
when swit
manuel aldana wrote:
> hi,
>
> i've got VS 2005 installed and cannot compile log4cxx (HEAD revision).
> in all build files (build.xml, apr-build.xml, aprutil-build.xml) i set
> debug property to false.
>
> while running ant i get following build error, which hint on the line
> number of aprutil-b
Curt Arnold wrote:
[...]
> I'm pretty sure that the message "Cannot get information about host:
> unknown.host.local" is unrelated to the test failure in
> "OptionConverterTestCase::testUserHome" in file
> tests/src/helpers/optionconvertertestcase.cpp.
Curt, you are absolutely right. I just checke
Hi Mark,
this is strange since it is the host name which is used
in the InetAddressTestCase to verify if the UnknownHostException
works properly. Just to be sure: can you change the string "unknown.host.local"
in line 70 of tests/src/helpers/inetaddresstestcase.cpp to something
different, like "un
Hi Stephane,
there is no issue with the windows build, other than
it is still not yet done automagically, while the linux
build is executed each night :-)
I will try to update the binaries in the next couple of days.
Thanks,
Andreas
stephane wrote:
> Hi,
>
> I just downloaded the log4c
Hi,
Listen wrote:
> Dear List,
>
> 1. I'm able to compile log4cxx from the HEAD revision from svn using the
> ant build system, but the size I'm getting out is much bigger than the
> one I found in http://littletux.homelinux.org/log4cxx. The size found
> in in the archive is about 497kB where mi
Arunkumar wrote:
> Hey Curt,
> Thanks for your suggestions. I will try to make the suggested changes and
> see what happens.
>
> My test bed is:
> OS: Windows XP SP2
> VisualStudio.Net 2003
> Text Editor: Notepad or MS Word (after your email, downloaded the SuperEdi
> Editor)
In the windows cmd.e
Jeffrey Graham wrote:
> Hello,
>
> How do I tell ant to build the ODBC stuff?
On which platform are you? On MS-Windows, it should always
compile with ODBC support (#define LOG4CXX_HAVE_ODBC 1
in the MS-Windows specific configuration header log4cxx.hw).
On UNIX, it seems that odbc is not yet supp
Hi Arunkumar,
> Hi Guys,
>
> I built the log4cxxd.dll using the default parameters (though one of the
> unit tests failed in the end. I had sed etc. in the PATH. OS: Windows XP
> Sp2. Env: VS.Net 2003). I included the dll in my test project and as soon as
> I ran it I get this pleasing error (log
Curt Arnold wrote:
>> I tried to build a release build (on a Windows XP SP2 machine) from the
>> trunk and it failed.
>> I had set the classpath to point to: C:\Program Files\Microsoft Visual
>> Studio .NET 2003\Vc7\bin instead of the normal vc6 batch file. I hope
>> that
>> was not the reason for
john ware wrote:
> I'm required to use the compiler from visualstudio and I use cygwin for
> launching ant only. I have modified build.xml to call cl.exe to build
Is there any specific reason why you are launching ant from cygwin?
ant can also perfectly be launched from a normal DOS shell with the
Hi,
Bruce Riley wrote:
[...]
> I'm not exactly sure what or how I should "recompile with -fPIC".
You dont need to, the compiler switches already include it.
On 64 bit platforms this message is sometimes seen as a side
result of something else, usually in conjunction with the
"relocation R_X86_64_
Hi,
I completed the porting of the network functions to the APR,
basically the InetAddress class was the one which did not
use the APR functions yet.
Since these are quite some changes, I would like to encourage
everyone to test it before I commit it; the dist-tarball containing
the patch is at h
Hi Ambarish,
Ambarish Mitra wrote:
[...]
> Therefore, the only difference is while in first case, I used Solaris ld,
> here I have GNU ld. Does it matter?
It should not. I am building the SVN Head each night (see
http://www.littletux.net/log4cxx) on Debian GNU/Linux using gcc 3.3.5.
[...]
> This
Matthew Kanwisher wrote:
> > I used svn head, but there was an ANT build file(its a bit tricky to
The same is true for the dist-tarball at
http://littletux.homelinux.org/log4cxx/ :-)
All you should have to do is to call "ant" in the log4cxx-0.9.8
directory.
Best Regards,
Andreas
Hi,
I intend to commit the attached patch. It re-adds the syslog
appender (fixes LOGCXX-66).
The memory leak which was reported some days ago should be fixed.
I dont really like the memory pools being passed from one
method to another (and probably this would not have helped here
because it would
Hi Marc,
Marc Respass wrote:
> Hi All,
>
> I'm new to the list and new to log4cxx. I've been trying to compile for
Welcome :-)
> Mac OS X Tiger (10.4.6 on Intel). I did a search and can't find anything
> that helps. I can't even get past the configure script. I got the latest
> release from Subv
Renato Cassaca wrote:
> I''m using Log4Cxx with STLPort and each time that I checkout Log4cxx I
> have to patch src/systemerrwriter.cpp and src/systemoutwriter.cpp and
> add the following line:
>#include
>
> Because "stdout" and "stderr" aren't found at compile time.
I dont think that its re
Matthew Campbell wrote:
> UGH your right mine says, its been a while so I probaly just forgot
> that I changed it. It seems log4cxx is rough around the edges
> sometimes.
>
> DECLARE_LOG4CXX_OBJECT(TimeBasedRollingPolicy)
> Double checked svn head, and your right it says
>DECLARE_ABS
Hi,
this is an issue which still occurs when compiling with
the SUN compiler, see
http://marc.theaimsgroup.com/?l=log4cxx-user&m=113473025221990&w=2
The #define __STDC_ISO_10646__ is not defined in this case.
You can try to remove lines 143 and 166 from src/unicodehelper.cpp
143: #if defined(_
Curt Arnold wrote:
>
> On Mar 9, 2006, at 4:15 AM, Efri Nattel-Shay wrote:
>
>> A couple of questions about the SyslogAppender:
>>
>>
>>
>> Any reason for the duplication of HAVE_SYSLOG and
>> LOG4CXX_HAVE_SYSLOG? The former exists in the makes, the latter is in
>> the sources itself. The sourc
Hi,
please use log4cxx 0.9.8, if anyhow possible. A daily
distribution tarball and binaries are available at
http://www.littletux.net/log4cxx/
I tried your application with it, and the output
without the property file is
0 [0x2d76b850] INFO MyApp null - Entering application.
1 [0x2d76b85
Ron,
which version of AIX are you using, and which compiler
(gcc/visual age; which version)?
Can you provide a minimal code example which causes the crash?
Thanks,
Andreas
Ron Ohmer wrote:
> During the destructor phase of Log4CXX we are experiencing core files
> being dropped. This hap
Bug report created, patch applied and committed :-)
Thanks,
Andreas
Efri Nattel-Shay wrote:
> When compiling 0.9.8 on a Linux FC5 machine, (g++ version 4.1), I'm
> getting two of the following errors.
> An svn diff of the interface without the extra qualification, that
> passes compilati
Yang Xiang wrote:
> I have a C++ app which was compiled and linked with log4cxx. I am using
> the default configuration
>
> log4j.rootLogger = DEBUG, A1
> log4j.appender.A1 = org.apache.log4j.ConsoleAppender
> log4j.appender.A1.layout = org.apache.log4j.PatternLayout
> log4j.appender.A1.layout.Co
Hi,
EXT / ALTIOR POINTE Jean-Baptiste (I&R) wrote:
> Thanks for your reply.
> I've downloaded the latest version 0.9.8 and tried to install but the
> following error
> occured while executing './autogen.sh':
You dont need to execute autogen.sh with my dist-tarball.
It already contains the confi
>> Is it unbearably hard to make the automake build to create a single
>> test executable without using an intermediate library? Breaking the
>> test suite up into a small driver and a shared library of tests has got
>> to make debugging in some IDE's more complicated than just having a
>> singl
Hi,
Which package do you use?
> c:\MinGW\bin\make.exe[1]: Entering directory `d:/Linux/log4cxx-0.9.7/docs'
This looks like you are using the outdated 0.9.7 version.
You should probably consider using the currently work-in-progress
version 0.9.8. Try the package from
http://www.littletux.net/log
Curt Arnold wrote:
> Is it unbearably hard to make the automake build to create a single
It is ;-)
> test executable without using an intermediate library? Breaking the
> test suite up into a small driver and a shared library of tests has got
> to make debugging in some IDE's more complicated
Hi,
the latest tarball from
http://www.littletux.net/log4cxx/log4cxx-0.9.8.tar.gz
is now compilable on Solaris (I verified it on Solaris 2.9
with gcc 3.3). The test cases also execute properly.
The main changes were to fix the detection of std::wstring
instead of wchar_t, to wrap some pieces of
J P Weber wrote:
> Which classes need to be registered in
> Class::registerClasses() (and why)? Is it the classes
> whose instances will be created "dynamically" by the
> configurators? Why aren't all of the filter classes
Basically, yes, the reason is that those classes can be
instanciated "by
Owens, Brad wrote:
> I just got further along using the "-Dhas.wchar_t=0" option, but build is
> now failing over the xml code:
>[cc]
> C:/testlab/log4cxx-20051201/log4cxx-0.9.8/include/log4cxx/helpers/gnomexml.h
> :2
> 7:25: libxml/tree.h: No such file or directory
This is usually caused
> The config and build went fine until the build-apr target, which failed
> due to the "with-apr" variable having the incorrect value. I tweaked
> line 496 of build.xml to fix the "with-apr" variable to be
> "../apr-${apr.version}/apr-1-config" instead of
> "../apr-${apr.version}/apr--config".
I
>[cc]
>
C:/testlab/log4cxx-20051201/log4cxx-0.9.8/include/log4cxx/helpers/loglog.h:92:
>
> error: expected unqualified-id before '&' token
there seems to be no wchar_t datatype available (or
at least no std::wstring). You could either try
the autotools approach with
$ ./configure ; make
Jitendra Kharche wrote:
> Thanks Jürgen.
> Exactly, I have the same problem. I am accessing the log file from multiple
> processes.
Note that this is not supported by log4j either.
There is no synchronization between different JVMs accessing the same
log file.
One possibility would be to use a so
Hi,
Anoop Philip wrote:
> I am a fresher in programing.In my project,currently trying to to
> implement log4cxx9.8(Using Win32console application in vc++6.0 and
> log4cxxd.lib).
I tried your application both on Linux and on MS-windows with the
Visual Studio .NET compiler, and it runs on both wit
Labour, Matthieu (MLPRO SF) wrote:
> Hi,
>
> I got the latest log4cxx-0.9.8 from
> http://littletux.homelinux.org/log4cxx/
>
> When I run ./autogen.sh
It should usually not be necessary to run autogen,
because the tarball at
http://littletux.homelinux.org/log4cxx/log4cxx-0.9.8.tar.gz
already con
Anastasios Angelidis wrote:
> I see that 0.9.7 has greate issues. Can I even trust the CVS head?
It also still has some issues ;-), and is still work
in progress.
You might want to try the dist-tarball at
http://www.littletux.net/log4cxx
This is identical to SVN head, but contains some additiona
Hi,
which source tree did you use, the SVN head or the one at
http://www.littletux.net/log4cxx ?
I just recompiled the dist-tarball
from http://www.littletux.net/log4cxx/log4cxx-0.9.8.tar.gz
using Visual Studio .NET which succeeded fine.
See http://www.littletux.net/log4cxx/log4cxx-0.9.8_win32.zi
ase null - message0
5 [main] DEBUG org.apache.log4j.NDCTestCase (a) - message1
5 [main] DEBUG org.apache.log4j.NDCTestCase null - message2
So, this is something which can also be discussed
on the log4j list after all, since the behaviour
of log4cxx is compliant to log4j in this case ;-)
Regards,
Andreas
(a)");
>
> logger->debug ("message1");
>
> log4cxx::NDC::pop ();
>
> logger->debug ("message2");
>
>
>
>
>
> was:
>
> .. (a) message1
>
> ... message2
>
>
>
> And now when I'm using the log4cxx-0.9.8 the result is:
>
> .. (a) message1
>
> ... null message2
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
_str());
> 270
> 271 return;
> 272 }
> 273 #endif
> ---
>
> As a stopgap, I "#define LOG4CXX 1", and "#include log4cxx_private.h>" in the "syslogappender.h" header file before the
> "LOG4CXX_HAVE_SYSLOG" precompiler variable gets checked. I'm assuming
> there's either something wrong in the way I'm doing things, or there's
> something wrong in the header files.
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
on to APR 1.2.2), and it also contains WIN32 binaries
and a build log from building those binaries.
It should usually be sufficient to have the right cpptask package
in place and call "ant" to build everything.
Best Regards,
Andreas
- --
Andreas Fester
mailto:[EMAIL P
-o test test.cpp
>
> And the result is:
> /tmp/ccUOHsmb.o: In function `__static_initialization_and_destruction_0(int,
> int)':
> test.cpp:(.text+0xda): undefined reference to
> `log4cxx::Logger::getLogger(char
> const*)'
> collect2: ld returned 1 exit status
) requires the *address* of
the apr_os_thread_t variable. Strangely the unittests succeeded
on my desktop linux box, but not during the nightly build on my
server ...
Corrected patch is attached.
Best Regards,
Andreas
- --
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326
.
Drawback(?): this specific format specifier for apr_os_thread_id
was introduced as new feature with APR 1.2, which would mean
that APR 1.2 will be mandatory (not a big issue in my opinion)
starting with this patch.
Any comments?
Thanks and best Regards,
Andreas
- --
Andreas Fester
mailto
x bugs when using it in
[...]
- --
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDWSdDZ3bQVzeW+rsRAqk1AJ9aG7Yqr+4Kv
fixes the unresolved symbols error which occured
in the SMTP appender.
- 52-logstream_export.diff exports the << operators from stream.h which
are used in the unit tests (and caused additional unresolved symbols).
Best Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTE
]
>
> [EMAIL PROTECTED]@log4cxx@@[EMAIL PROTECTED]@[EMAIL PROTECTED])
>
>[cc] class.obj : error LNK2001: unresolved external symbol "public:
> virtual __thiscall log4cx
>
> x::net::SMTPAppender::~SMTPAppender(void)"
> ([EMAIL PROTECTED]@log4cxx@@[EMAIL PROTE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have started a Wiki for log4cxx at
http://wiki.apache.org/logging-log4cxx/
Currently, it only contains some of the more frequently asked
questions, but any contribution is welcome!
Best Regards,
Andreas
- --
Andreas Fester
mailto
se.cpp:115: `::fork' undeclared (first use here)
socketservertestcase.cpp:117: `::execl' undeclared (first use here)
socketservertestcase.cpp:124: `sleep' undeclared (first use this
[...]
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
tion: static - Win32
[...]
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littletux.net
ICQ: 326674288
to implement the abstract function
virtual void append(const spi::LoggingEventPtr& event,
log4cxx::helpers::Pool& p) = 0;
from AppenderSkeleton to implement your specific logging functionality.
Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://www.littl
Hi Javier,
inking...
MyPrueba.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) public: void
__thiscall log4cxx::Logger::forcedLog(class log4cxx::helpers::ObjectPtrT
const &,class std::basic_string,class std::allocator > const &,char const *,int)" ([EMAIL
PROTECTED]@log4c
Hi Sandip,
Can you provide me with the log4cxx version that is
error free ans should work for windows and unix.
IMHO "error free code" does not exist ;-)
You can get the latest (unofficial) 0.9.8 build at
http://www.littletux.net/log4cxx
It should build at least on Linux and Windows, and co
because many classes are configured
by name in the .properties or .xml configuration file, for example the
appenders).
Is there some documentation about these macros?
$ vi include/log4cxx/helpers/object.h ;-)
Best Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http
Hi,
Alex Raimondi wrote:
Hi
I tried to subclass class HTMLLayout, but I get a lot of strange linking
errors.
- Which log4cxx version are you using (0.9.7 or 0.9.8)?
- *What are* the linker errors?
Best Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http
Original Message
Subject: RE: cpptasks.jar and ant-contrib.jar
Date: Mon, 1 Aug 2005 13:14:49 -0400
From: cakebread, ken (pj) <[EMAIL PROTECTED]>
To: 'Andreas Fester' <[EMAIL PROTECTED]>
Hi
The new CppTasks is nowhere to be found.
Plus, on Windows, we
nment, but before
submitting a patch, I want to finish the work I started some
time ago (porting network related stuff to APR) by also porting
the DatagrammSocket.
Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
as pushed. Is this how things are meant to be?
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
Index: include/log4cxx/ndc.h
===
RCS file: /home/cvspublic/logging-log4cxx/include/log4cxx/ndc.h
as the java SimpleDateFormat class.
I checked the 0.9.8 patternlayout implementation and adjusted
the documentation accordingly (patch attached).
Best Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
Index: include/log4cxx
Unix because, as far as I can see, apr_strftime is used and
that is just a front for strftime which of course just works with
seconds. So the documented %Q format element is just treated like
run-of-the-mill characters and not interpreted.
[...]
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW:
Hi,
[...]
Hmm, installed apr 1.1.1, apr-util 1.1.2, got a new snapshot of log4cxx
CVS and this is what happens at compile time:
you need to pass --with-logchar=wchar_t to the configure script.
The default for logchar is already changed to utf8 in my dist-tarball
package, but the simpledateform
Hi Allen,
Conway Allen wrote:
Hello,
I've picked up Andreas' dist-tarball and various other things (apr, apr-util,
etc) which I've installed on my old Debian Linux 2.2.20. I've run autogen.sh and
you should usually not need to run autogen.sh, because the dist-tarball
already contains the pr
@" is not valid in preprocessor expressions make[1]: *** [action.lo]
> Error 1
>
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
Hi,
I would like to take this to discuss one thing I thought about
when working on log4cxx and creating the Debian packages:
Is 0.9.8 really the correct version number?
Background: The SO_NAME of the 0.9.7 library was "9", so we have to
change it before log4cxx is released, because 0.9.8 is
oIt()':
../log4cxx/include/log4cxx/helpers/objectptr.h:88: undefined
reference to
`log4cxx::Logger::forcedLog(log4cxx::helpers::ObjectPtrT
const&, _STL::basic_string,
_STL::allocator > const&, log4cxx::spi::LocationInfo const&)'
collect2: ld returned 1 ex
Hi Pedro,
Pedro Monjo Florit wrote:
Hi everybody,
I have succesfully compiled log4cxx CVS HEAD, using the ant build
system. The next problem I am facing is installation. With version
0.9.7, there was the traditional *nix method of "configure", "make" and
"make install", so it was fairly easy
maryline royer wrote:
Could somebody send me cpptasks.jar and ant-contrib.jar to compile
log4cxx cvs version.
Thanks.
$ grep -m2 -A4 cpptasks INSTALL
Ant + cpptasks build:
==
The Ant build script is the definitive build script for log4cxx and
is able to build log4cxx with (a
Hi,
you can try using this package:
http://littletux.homelinux.org/debian/log4cxx/log4cxx_0.9.7.orig.tar.gz
it is identical to log4cxx_0.9.7,tar.gz from the apache site, but
already contains the configure script so that it can be built with
the usual ./configure; make without calling automake.
figurator.java:687)
at ch.consultas.osp.webcrawling.Log.initialize(Log.java:72)
at mypackage1.Hello.main(Hello.java:20)
Debugger disconnected from local process.
Process exited.
Can you help me?
Raoul
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
import org.apache.log4j.*;
impo
lt;<(log4cxx::logstream&, char const*)':
log4cxx/stream.h:153: multiple definition of `operator<<(log4cxx::logstream&,
char const*)'
[...]
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.
make
as usual.
Best Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
s. So
something like
logstream info(logger, Level::INFO);
info << "In src1.cpp" << 4.5 << " / " << 4;
seems a proper solution for me.
Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
Hi,
Keith Bottner wrote:
Hey all I once more put forth a request for some guidance on getting
log4cxx compiling on FreeBSD 5.3-RELEASE.
Since log4cxx-0.9.7.tar.gz does not come with a ./configure all ready to
Due to this, I also had some hard time to create the Debian packages
which I currently
pache\logging-log4cxx\build\release\
static" msi.lib log4cxx.lib objectfile1.obj objectfile2.obj
should do the job). This sort of approach usually helps me in finding
such errors :-)
Regards,
Andreas
--
Andreas Fester
mailto:[EMAIL PROTECTED]
WWW: http://littletux.homelinux.org
ICQ: 326674288
85 matches
Mail list logo
