RE: [Log4cpp-devel] Compiling with sun CC

[<hel...@ed...>]

Yeah, that seems to do the trick!

Perhaps this could go down into a FAQ or something for
other people to take advantage of?

First test ran OK, but the second came up with:

CC -DHAVE_CONFIG_H -I. -I. -I../include -I../include    -g -c Clock.cpp
"Clock.cpp", line 47: Error: endl is not defined.
1 Error(s) detected.

some std:: missing, perhaps.

We are thinking about using this library in our software. Has
anyone run purify on this code to check for memory leaks? Any
routine on that before you ship new releases?

How about connection to the Lumbermill GUI/Log server? I see
that it's missing a SocketAppender class, so this probably=20
haven't been tested? Should be easy to add such a class, though?

Best regards,
Helge Fredriksen

-----Original Message-----
From: Bastiaan Bakker [mailto:Bas...@li...]
Sent: 1. februar 2002 15:23
To: Fredriksen Helge (4tel); log...@li...
Subject: RE: [Log4cpp-devel] Compiling with sun CC


Hmm, this looks suspiciously like the sun CC compile problems discussed
earlier on this list. Does=20
CC=3DCC CXX=3DCC LD=3D"CC -KPIC" ./configure --disable-static=20
work?

Cheers,

Bastiaan

> -----Original Message-----
> From: hel...@ed...=20
> [mailto:hel...@ed...]
> Sent: Friday, February 01, 2002 12:07 PM
> To: log...@li...
> Subject: [Log4cpp-devel] Compiling with sun CC
>=20
>=20
> Hay there!
>=20
> I've just been trying to compile log4cpp with Sun CC native=20
> compiler (Forte
> 6.2).
> I was not very successful using the configure program for=20
> this: Giving the=20
> arguments "CC=3DCC CXX=3DCC ./configure" produced Makefiles OK,=20
> the lib were
> produced, but when I tried to link it to one of the test=20
> executables, lot's
> of symbols
> didn't get recognized.=20
>=20
> However, I made my own Makefiles which worked fine, I'm=20
> sharing them with
> you in case you want to incorporate this stuff into your make=20
> regime...
>=20
>  <<Makefile.src>>  <<Makefile.test>>=20
> Best regards,
> Helge Fredriksen
>=20