can't make apache-log4cxx-0.10.0

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

can't make apache-log4cxx-0.10.0

Andreas Meyer
Hello!

After the ./configure run, the make command gives me the following error:

inputstreamreader.cpp: In member function 'virtual log4cxx::LogString log4cxx::helpers::InputStreamReader::read(log4cxx::helpers::Pool&)':
inputstreamreader.cpp:66:64: error: 'memmove' was not declared in this scope
make[3]: *** [inputstreamreader.lo] Fehler 1
make[3]: Leaving directory `/home/mail1/apache-log4cxx-0.10.0/src/main/cpp'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/home/mail1/apache-log4cxx-0.10.0/src/main'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/mail1/apache-log4cxx-0.10.0/src'
make: *** [all-recursive] Fehler 1

Every help is very much appreciated!

  Andreas
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Rhys Ulerich-2
> inputstreamreader.cpp: In member function 'virtual log4cxx::LogString log4cxx::helpers::InputStreamReader::read(log4cxx::helpers::Pool&)':
> inputstreamreader.cpp:66:64: error: 'memmove' was not declared in this scope

Please try using SVN trunk, that's a known issue which has been fixed.

- Rhys
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Thorsten Schöning
In reply to this post by Andreas Meyer
Guten Tag Andreas Meyer,
am Freitag, 16. Mai 2014 um 18:10 schrieben Sie:

> Every help is very much appreciated!

Please use a trunk checkout using Subversion, a lot of bug fixes have
been applied during the last month, which just didn't make it into a
official release yet. Besides that, the current trunk passes all tests
and has been tested by other users. If your problem persist, please
provide some more details like the compiler or IDE you use, which
platform etc.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning       E-Mail:[hidden email]
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Andreas Meyer
Hello!

Thorsten Schöning <[hidden email]> schrieb am 16.05.14 um 23:40:33 Uhr:

> Guten Tag Andreas Meyer,
> am Freitag, 16. Mai 2014 um 18:10 schrieben Sie:
>
> > Every help is very much appreciated!
>
> Please use a trunk checkout using Subversion, a lot of bug fixes have
> been applied during the last month, which just didn't make it into a
> official release yet. Besides that, the current trunk passes all tests
> and has been tested by other users. If your problem persist, please
> provide some more details like the compiler or IDE you use, which
> platform etc.

I got it like this:
svn checkout http://svn.apache.org/repos/asf/incubator/log4cxx/trunk apache-log4cxx

but there is no configure script in the directory.

What to do now?

  Andreas
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Andreas Meyer
In reply to this post by Rhys Ulerich-2
Hello!

Rhys Ulerich <[hidden email]> schrieb am 16.05.14 um 15:43:28 Uhr:

> > inputstreamreader.cpp: In member function 'virtual log4cxx::LogString log4cxx::helpers::InputStreamReader::read(log4cxx::helpers::Pool&)':
> > inputstreamreader.cpp:66:64: error: 'memmove' was not declared in this scope
>
> Please try using SVN trunk, that's a known issue which has been fixed.

I got the trunk, but how do I compile it?

> - Rhys

  Andreas
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Rhys Ulerich-2
In reply to this post by Andreas Meyer
> svn checkout http://svn.apache.org/repos/asf/incubator/log4cxx/trunk apache-log4cxx
> but there is no configure script in the directory.

Run ./autogen.sh to generate the autotools details, like configure.

- Rhys
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Andreas Meyer
Hello Rhys!

Rhys Ulerich <[hidden email]> schrieb am 17.05.14 um 00:59:54 Uhr:

> > svn checkout http://svn.apache.org/repos/asf/incubator/log4cxx/trunk apache-log4cxx
> > but there is no configure script in the directory.
>
> Run ./autogen.sh to generate the autotools details, like configure.

That did it! I get the following after a sudo make install:

....
 /usr/bin/mkdir -p '/usr/local/include/log4cxx'
 /usr/bin/install -c -m 644 ../../../../src/main/include/log4cxx/appender.h ../../../../src/main/include/log4cxx/appenderskeleton.h ../../../../src/main/include/log4cxx/asyncappender.h ../../../../src/main/include/log4cxx/basicconfigurator.h ../../../../src/main/include/log4cxx/consoleappender.h ../../../../src/main/include/log4cxx/dailyrollingfileappender.h ../../../../src/main/include/log4cxx/defaultconfigurator.h ../../../../src/main/include/log4cxx/defaultloggerfactory.h ../../../../src/main/include/log4cxx/fileappender.h ../../../../src/main/include/log4cxx/file.h ../../../../src/main/include/log4cxx/hierarchy.h ../../../../src/main/include/log4cxx/htmllayout.h ../../../../src/main/include/log4cxx/layout.h ../../../../src/main/include/log4cxx/level.h ../../../../src/main/include/log4cxx/log4cxx.h ../../../../src/main/include/log4cxx/logger.h ../../../../src/main/include/log4cxx/logmanager.h ../../../../src/main/include/log4cxx/logstring.h ../../../../src/main/include/log4cxx/mdc.h ../../../../src/main/include/log4cxx/ndc.h ../../../../src/main/include/log4cxx/patternlayout.h ../../../../src/main/include/log4cxx/portability.h ../../../../src/main/include/log4cxx/propertyconfigurator.h ../../../../src/main/include/log4cxx/provisionnode.h ../../../../src/main/include/log4cxx/rollingfileappender.h ../../../../src/main/include/log4cxx/simplelayout.h ../../../../src/main/include/log4cxx/stream.h ../../../../src/main/include/log4cxx/ttcclayout.h ../../../../src/main/include/log4cxx/writerappender.h ../../../../src/main/include/log4cxx/appender.h ../../../../src/main/include/log4cxx/appenderskeleton.h ../../../../src/main/include/log4cxx/asyncappender.h ../../../../src/main/include/log4cxx/basicconfigurator.h ../../../../src/main/include/log4cxx/consoleappender.h ../../../../src/main/include/log4cxx/dailyrollingfileappender.h ../../../../src/main/include/log4cxx/defaultconfigurator.h ../../../../src/main/include/log4cxx/defaultloggerfactory.h ../../../../src/main/include/log4cxx/fileappender.h ../../../../src/main/include/log4cxx/file.h ../../../../src/main/include/log4cxx/hierarchy.h '/usr/local/include/log4cxx'
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/appender.h“ wird nicht mit „../../../../src/main/include/log4cxx/appender.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/appenderskeleton.h“ wird nicht mit „../../../../src/main/include/log4cxx/appenderskeleton.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/asyncappender.h“ wird nicht mit „../../../../src/main/include/log4cxx/asyncappender.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/basicconfigurator.h“ wird nicht mit „../../../../src/main/include/log4cxx/basicconfigurator.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/consoleappender.h“ wird nicht mit „../../../../src/main/include/log4cxx/consoleappender.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/dailyrollingfileappender.h“ wird nicht mit „../../../../src/main/include/log4cxx/dailyrollingfileappender.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/defaultconfigurator.h“ wird nicht mit „../../../../src/main/include/log4cxx/defaultconfigurator.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/defaultloggerfactory.h“ wird nicht mit „../../../../src/main/include/log4cxx/defaultloggerfactory.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/fileappender.h“ wird nicht mit „../../../../src/main/include/log4cxx/fileappender.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/file.h“ wird nicht mit „../../../../src/main/include/log4cxx/file.h“ überschrieben.
/usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/hierarchy.h“ wird nicht mit „../../../../src/main/include/log4cxx/hierarchy.h“ überschrieben.
make[6]: *** [install-log4cxxincHEADERS] Fehler 1
make[6]: Leaving directory `/home/mail1/apache-log4cxx/src/main/include/log4cxx'
make[5]: *** [install-am] Fehler 2
make[5]: Leaving directory `/home/mail1/apache-log4cxx/src/main/include/log4cxx'
make[4]: *** [install-recursive] Fehler 1
make[4]: Leaving directory `/home/mail1/apache-log4cxx/src/main/include/log4cxx'
make[3]: *** [install-recursive] Fehler 1
make[3]: Leaving directory `/home/mail1/apache-log4cxx/src/main/include'
make[2]: *** [install-recursive] Fehler 1
make[2]: Leaving directory `/home/mail1/apache-log4cxx/src/main'
make[1]: *** [install-recursive] Fehler 1
make[1]: Leaving directory `/home/mail1/apache-log4cxx/src'
make: *** [install-recursive] Fehler 1

The directory /usr/local/include/log4cxx with its content is created
nevertheless. Is this ok?

Also

delta:/usr/local/lib # ll
insgesamt 28464
-rw-r--r-- 1 root root 18883006 17. Mai 09:52 liblog4cxx.a
-rwxr-xr-x 1 root root     1019 17. Mai 09:52 liblog4cxx.la
lrwxrwxrwx 1 root root       20 17. Mai 09:52 liblog4cxx.so -> liblog4cxx.so.10.0.0
lrwxrwxrwx 1 root root       20 17. Mai 09:52 liblog4cxx.so.10 -> liblog4cxx.so.10.0.0
-rwxr-xr-x 1 root root 10037757 17. Mai 09:52 liblog4cxx.so.10.0.0
-rw-r--r-- 1 root root   107804 18. Dez 23:50 liblufs-cryptofs.a
-rwxr-xr-x 1 root root      903 18. Dez 23:50 liblufs-cryptofs.la
lrwxrwxrwx 1 root root       25 18. Dez 23:50 liblufs-cryptofs.so -> liblufs-cryptofs.so.0.0.6
lrwxrwxrwx 1 root root       25 18. Dez 23:50 liblufs-cryptofs.so.0 -> liblufs-cryptofs.so.0.0.6
-rwxr-xr-x 1 root root    97468 18. Dez 23:50 liblufs-cryptofs.so.0.0.6
drwxr-xr-x 3 root root     4096  2. Mai 00:12 lua

seems to be fine.

> - Rhys

  Andreas
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Rhys Ulerich-2
> /usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/appender.h“ wird nicht mit „../../../../src/main/include/log4cxx/appender.h“ überschrieben.

Are these complaints that /usr/bin/install refuses to overwrite one
file with another (guessing "uberschrieben" is "overwritten")?  I'm
aware of some hiccups with this in the current build which I plan to
clean up soon.  The problem, if this is what I think it is, is that
the Makefiles specify some wildcard headers which are incorrect per
Automake semantics.  To fix this, I need to double check both an
in-tree and and a VPATH build works correctly, which I've been putting
off.  I'll try to get to this this weekend.

- Rhys
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

Andreas Meyer
Hello!

Rhys Ulerich <[hidden email]> schrieb am 17.05.14 um 12:23:01 Uhr:

> > /usr/bin/install: Neu erstelltes „/usr/local/include/log4cxx/appender.h“ wird nicht mit „../../../../src/main/include/log4cxx/appender.h“ überschrieben.
>
> Are these complaints that /usr/bin/install refuses to overwrite one
> file with another (guessing "uberschrieben" is "overwritten")?  I'm

yes, so it is. The make install installs the files and warns that they
would be overwritten.

> aware of some hiccups with this in the current build which I plan to
> clean up soon.  The problem, if this is what I think it is, is that
> the Makefiles specify some wildcard headers which are incorrect per
> Automake semantics.  To fix this, I need to double check both an
> in-tree and and a VPATH build works correctly, which I've been putting
> off.  I'll try to get to this this weekend.

allright, log4cxx installed nevertheless and is found by other
compiling processes.

> - Rhys

Thank you!

  Andreas
Reply | Threaded
Open this post in threaded view
|

Re: can't make apache-log4cxx-0.10.0

thebunnyrules
This post has NOT been accepted by the mailing list yet.
In reply to this post by Rhys Ulerich-2
Rhys, thanks for your help, I was struggling with the same issues. I want to make a correction to one of your statements as it lead me to some confusion and I'd thought I'd put this correction up in case some other fellow newbs would get confused by it too:

You said to use autogen.sh instead of configure. You actually have to use autogen.sh and then use ./configure afterwards, followed by make make etc....