OK, I managed to answer question 2 for myself. log4cxx will build on RHEL3.8 with GCC3.2.3. However the build of the unit tests fails in socketservertestcase.cpp. This doesn't really effect me, the log4ccx library has been built so I can move forward. If the problem building socketservertestcase.cpp is something you want to look into let me know and I'll provide more info from the build.
So now I'll try GCC 4.1.1 on Windows. Is there anywhere to download this in a ready-to-go state or do I need to build it for myself? On 5/8/07, Ken Klose <[EMAIL PROTECTED]> wrote:
Curt, Thanks for you all your help! I tried the steps using the GCC thats in the MinGW distribution (3.4.2) and it didn't work. So I'd like to try it with 4.1.1. A couple of questions: 1. Where did you get MinGW with GCC 4.1.1? Or where can I get GCC4.1.1for MinGW? 2. Will log4cxx build on linux with GCC 3.2.3? Right now I'm working on Windows, but I have to deliver to developers run RHEL3.8 with GCC3.2.3. I'm going to try build in on linux now unless you know it won't work. I really appreciate all your help, I'd be lost without it! Thanks, Ken On 5/8/07, Curt Arnold <[EMAIL PROTECTED]> wrote: > > > On May 5, 2007, at 1:48 PM, Ken Klose wrote: > > > Curt, > > > > Thanks for the help. That indeed got me further along! I built > > against last night's snapshot of APR, made the changes you said to > > apr.h and got it to build. Now I'm getting an error in the build > > of log4cxx itself. "no type named `pos_type'" "in `struct > > std::char_traits<wchar_t>'", "in `class > > std::basic_ostream<localechar, std::char_traits<wchar_t> >'" and > > "in `class std::basic_stringbuf<localechar, > > std::char_traits<wchar_t>, std::allocator<wchar_t> >'", > > > > > > Thanks, > > Ken > > > > I'm thinking that might be a gcc issue that is fixed in gcc 4.1.1. > If you review the archives around last december, there should be a > decent amount of MinGW discussion. I only remembered why I had a > MinGW gcc 4.1.1 around way late in this experiment and haven't gone > back and checked the archives and must get sleep now, so I'm posting > this incomplete bit of research in case it might help you. > > I was able to build log4cxx and run the unit tests using the MSYS > 1.0.10, gcc 4.1.1 and the make build. Didn't try with gcc 3.4.2. > The procedure was roughly > > Install MSYS 1.0.10 and MSYSdtk-1.0.1 > Install Active State Python 2.5 > Download and expand expat-2.0.0 and cppunit-1.10.2 > build and install expat-2.0.0 under MSYS > cd /c/expat-2.0.0 > ./configure > make install > build and install cppunit-1.10.2 under MSYS > cd /c/cppunit-1.10.2 > ./configure > make install > build and install apr SVN HEAD > cd /c/apr > export PATH=/c/python25:$PATH > ./buildconf > ./configure > make install > build and install apr-iconv SVN HEAD (might be unnecessary) > cd /c/apr-iconv > ./buildconf > ./configure --with-apr=/usr/local > make install > build and install apr-util SVN HEAD > cd /c/apr-util > ./buildconf > ./configure --with-apr=/usr/local --with-expat=/usr/local --with- > apr-iconv=/usr/local > make install > build log4cxx > cd /c/log4cxx > ./autogen.sh > ./configure --with-apr=/usr/local --with-expat=/usr/local --with- > apr-util=/usr/local --with-cppunit=/usr/local > Edit include/log4cxx.h changing LOG4CXX_LOGCHAR_IS from UTF_8 to > WCHAR > make check > > > > > > >
