You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-user@logging.apache.org by srkraju <ra...@cmcltd.com> on 2008/07/03 06:02:36 UTC
RE: MAKE error : While compiling trivial.cpp:Urgent
Dear curt, I tried to commented the calls and getting the following error
while I try to compile on Redhat Linux AS4(g++3.4.3). Kindly assist me to
solve this issue.
thanks& regards
srkraju
~-----Original Message-----
~From: Curt Arnold [mailto:carnold@apache.org]
~Sent: Saturday, June 21, 2008 2:19 AM
~To: Log4CXX User
~Subject: Re: MAKE error : While compiling trivial.cpp:Urgent
~
~
~On Jun 20, 2008, at 6:48 AM, srkraju wrote:
~
~> Dear Curt,
~> Thanks for your response.
~> Do you mean: commenting all LOG4CXX_XXXX calls in trivial.cpp.
~> And adding :: log4cxx::helpers::MessageBuffer oss; in trivial.cpp
~>
~> I did the above steps. But it is giving like
~> trivial.cpp:30: error: `BasicConfigurator' has not been declared
~> trivial.cpp:30: error: `configure' undeclared (first use this
~> function)
~> trivial.cpp:30: error: (Each undeclared identifier is reported only
~> once for
~> each function it appears in.)
~> trivial.cpp:33: error: `NDC' has not been declared
~> trivial.cpp:33: error: `push' undeclared (first use this function)
~> trivial.cpp:41: error: `NDC' has not been declared
~> trivial.cpp:41: error: `pop' undeclared (first use this function)
~>
~> if I comment the above lines then it is giving same errors in other
~> files.
~> Shall I continue in the same way. If so, what happens if any
~> LOG4CXX_XXXX
~> call made in our programs. Awaiting your response.
~>
~> thanks& regards
~> srkraju
~>
~
~
~I've set up a virtual machine running CentOS 4.0 x86 which comes with
~gcc 3.4.3 and did not have any issues. There have been no other
~reports of similar catastrophic failures to compile. It looks very
~much like a local machine issue and would be difficult for anyone to
~diagnose remotely. It almost appears that your header files are empty
~or that you've removed the include directives or using namespace
~directives from the source file.
DISCLAIMER
“The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you"
RE: MAKE error : While compiling trivial.cpp:Urgent
Posted by David Tran <dt...@yahoo-inc.com>.
If you installed apr and apr-utils to anywhere besides usr/local, I
think you have to use the --with-apr and --with-apr-util options. I
still had problems getting this to work on my machine, so I eventually
just built it all using ant, which will build apr and apr-utils from
their source as well.
-----Original Message-----
From: srkraju [mailto:ramaras@cmcltd.com]
Sent: Wednesday, July 02, 2008 11:28 PM
To: 'Log4CXX User'
Subject: RE: MAKE error : While compiling trivial.cpp:Urgent
When I give the ./configure command in apache-0.10.0 directory.
It is giving following error:
configure: error: APR could not be located. Please use
the
--with-apr option.
What may the problem? Is with-apr option is required or can we skip that
from compiling.
thanks& regards
srkraju
~-----Original Message-----
~From: Curt Arnold [mailto:carnold@apache.org]
~Sent: Thursday, July 03, 2008 11:18 AM
~To: Log4CXX User
~Subject: Re: MAKE error : While compiling trivial.cpp:Urgent
~
~
~On Jul 2, 2008, at 11:02 PM, srkraju wrote:
~
~> Dear curt, I tried to commented the calls and getting the following
~> error
~> while I try to compile on Redhat Linux AS4(g++3.4.3). Kindly assist
~> me to
~> solve this issue.
~>
~> thanks& regards
~> srkraju
~
~ From my previous message:
~>
~> ~
~> ~I've set up a virtual machine running CentOS 4.0 x86 which comes
with
~> ~gcc 3.4.3 and did not have any issues. There have been no other
~> ~reports of similar catastrophic failures to compile. It looks very
~> ~much like a local machine issue and would be difficult for anyone to
~> ~diagnose remotely. It almost appears that your header files are
~> empty
~> ~or that you've removed the include directives or using namespace
~> ~directives from the source file.
~>
~
~As far as I can tell, there is something specific to your machine that
~is causing the problem. If there is another developer who could take
~a look at the problem, he might track down the issue faster. If not,
~I would suggest the following:
~
~Download apache-log4cxx-0.10.0.tar.gz. The following assumes it was
~downloaded to ~/downloads:
~
~$ mkdir newdir
~$ cd newdir
~$ tar -xvzf ~/downloads/apache-log4cxx-0.10.0.tar.gz
~$ cd apache-log4cxx-0.10.0
~$ ./configure
~$ make
~
~Based on your reports, you should have completed the previous commands
~without problems,
~
~Then try
~
~$ make check
~
~If that completes successfully, then you have successfully built
~trivial and you can run it using
~
~$ src/examples/cpp/trivial
~
~If the make succeeded, there is some local change to the original
~log4cxx source that is responsible for the compile failures.
~
~If "make check" failed with the previously reported compile failures,
~then try:
~
~$ rm src/examples/trivial.o
~$ rm src/examples/trivial
~$ make CXXFLAGS=-E check
~
~That should create a trivial.o which is the preprocessor output and
~not actually an object file. Rename and attempt to compile this file
~to see if you get the same errors:
~
~$ cd src/examples/cpp
~$ mv trivial.o test.cpp
~$ gcc -c test.cpp
~
~If that fails, compress test.cpp, create a new JIRA bug report
~(http://issues.apache.org/JIRA/browse/LOGCXX
~) and attach test.cpp.gz.
~
~$ gzip test.cpp
DISCLAIMER
"The information contained in this e-mail message and/or attachments to
it may contain confidential or privileged information. If you are not
the intended recipient, any dissemination, use, review, distribution,
printing or copying of the information contained in this e-mail message
and/or attachments to it are strictly prohibited. If you have received
this communication in error, please notify us by reply e-mail or
telephone and immediately and permanently delete the message and any
attachments. Thank you"
Re: MAKE error : While compiling trivial.cpp:Urgent
Posted by Curt Arnold <ca...@apache.org>.
On Jul 3, 2008, at 1:27 AM, srkraju wrote:
> When I give the ./configure command in apache-0.10.0 directory.
> It is giving following error:
> configure: error: APR could not be located. Please use the
> --with-apr option.
>
> What may the problem? Is with-apr option is required or can we skip
> that
> from compiling.
--with-apr and --with-apr-util are required if apr and apr-util are
not in the expected location (typically /usr/lib). If you built and
installed APR and APR-Util yourself, you may need to specify:
./configure --with-apr=/usr/local/lib --with-apr-util=/usr/local/lib
RE: MAKE error : While compiling trivial.cpp:Urgent
Posted by srkraju <ra...@cmcltd.com>.
When I give the ./configure command in apache-0.10.0 directory.
It is giving following error:
configure: error: APR could not be located. Please use the
--with-apr option.
What may the problem? Is with-apr option is required or can we skip that
from compiling.
thanks& regards
srkraju
~-----Original Message-----
~From: Curt Arnold [mailto:carnold@apache.org]
~Sent: Thursday, July 03, 2008 11:18 AM
~To: Log4CXX User
~Subject: Re: MAKE error : While compiling trivial.cpp:Urgent
~
~
~On Jul 2, 2008, at 11:02 PM, srkraju wrote:
~
~> Dear curt, I tried to commented the calls and getting the following
~> error
~> while I try to compile on Redhat Linux AS4(g++3.4.3). Kindly assist
~> me to
~> solve this issue.
~>
~> thanks& regards
~> srkraju
~
~ From my previous message:
~>
~> ~
~> ~I've set up a virtual machine running CentOS 4.0 x86 which comes with
~> ~gcc 3.4.3 and did not have any issues. There have been no other
~> ~reports of similar catastrophic failures to compile. It looks very
~> ~much like a local machine issue and would be difficult for anyone to
~> ~diagnose remotely. It almost appears that your header files are
~> empty
~> ~or that you've removed the include directives or using namespace
~> ~directives from the source file.
~>
~
~As far as I can tell, there is something specific to your machine that
~is causing the problem. If there is another developer who could take
~a look at the problem, he might track down the issue faster. If not,
~I would suggest the following:
~
~Download apache-log4cxx-0.10.0.tar.gz. The following assumes it was
~downloaded to ~/downloads:
~
~$ mkdir newdir
~$ cd newdir
~$ tar -xvzf ~/downloads/apache-log4cxx-0.10.0.tar.gz
~$ cd apache-log4cxx-0.10.0
~$ ./configure
~$ make
~
~Based on your reports, you should have completed the previous commands
~without problems,
~
~Then try
~
~$ make check
~
~If that completes successfully, then you have successfully built
~trivial and you can run it using
~
~$ src/examples/cpp/trivial
~
~If the make succeeded, there is some local change to the original
~log4cxx source that is responsible for the compile failures.
~
~If "make check" failed with the previously reported compile failures,
~then try:
~
~$ rm src/examples/trivial.o
~$ rm src/examples/trivial
~$ make CXXFLAGS=-E check
~
~That should create a trivial.o which is the preprocessor output and
~not actually an object file. Rename and attempt to compile this file
~to see if you get the same errors:
~
~$ cd src/examples/cpp
~$ mv trivial.o test.cpp
~$ gcc -c test.cpp
~
~If that fails, compress test.cpp, create a new JIRA bug report
~(http://issues.apache.org/JIRA/browse/LOGCXX
~) and attach test.cpp.gz.
~
~$ gzip test.cpp
DISCLAIMER
“The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you"
Re: MAKE error : While compiling trivial.cpp:Urgent
Posted by Curt Arnold <ca...@apache.org>.
On Jul 2, 2008, at 11:02 PM, srkraju wrote:
> Dear curt, I tried to commented the calls and getting the following
> error
> while I try to compile on Redhat Linux AS4(g++3.4.3). Kindly assist
> me to
> solve this issue.
>
> thanks& regards
> srkraju
From my previous message:
>
> ~
> ~I've set up a virtual machine running CentOS 4.0 x86 which comes with
> ~gcc 3.4.3 and did not have any issues. There have been no other
> ~reports of similar catastrophic failures to compile. It looks very
> ~much like a local machine issue and would be difficult for anyone to
> ~diagnose remotely. It almost appears that your header files are
> empty
> ~or that you've removed the include directives or using namespace
> ~directives from the source file.
>
As far as I can tell, there is something specific to your machine that
is causing the problem. If there is another developer who could take
a look at the problem, he might track down the issue faster. If not,
I would suggest the following:
Download apache-log4cxx-0.10.0.tar.gz. The following assumes it was
downloaded to ~/downloads:
$ mkdir newdir
$ cd newdir
$ tar -xvzf ~/downloads/apache-log4cxx-0.10.0.tar.gz
$ cd apache-log4cxx-0.10.0
$ ./configure
$ make
Based on your reports, you should have completed the previous commands
without problems,
Then try
$ make check
If that completes successfully, then you have successfully built
trivial and you can run it using
$ src/examples/cpp/trivial
If the make succeeded, there is some local change to the original
log4cxx source that is responsible for the compile failures.
If "make check" failed with the previously reported compile failures,
then try:
$ rm src/examples/trivial.o
$ rm src/examples/trivial
$ make CXXFLAGS=-E check
That should create a trivial.o which is the preprocessor output and
not actually an object file. Rename and attempt to compile this file
to see if you get the same errors:
$ cd src/examples/cpp
$ mv trivial.o test.cpp
$ gcc -c test.cpp
If that fails, compress test.cpp, create a new JIRA bug report (http://issues.apache.org/JIRA/browse/LOGCXX
) and attach test.cpp.gz.
$ gzip test.cpp