[Dar-libdar_api] Re: problem compiling KDar with libdar CVS
For full, incremental, compressed and encrypted backups or archives
Brought to you by:
edrusb
|
From: Denis C. <dar...@fr...> - 2004-11-01 11:42:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Johnathan, There is two points I see about the API: - - first, since I have added multi-language support (the gettext function comes from here), I have not yet reviewed the general installation process, maybe there is some points to review about installed header files...(this will be done before pre-release phase, which target is december 2004). - - second, there is still changes to come in the API as discussed in this forum (see details bellow). I will look at this soon, as I am about to finish the implementation about the strong encryption features. Before pre-release phase, I will send a mail to this mailing list for an API review before release. I expect it before half november. Things to review in the API are : - - op_create & other functions must become methods of the archive class (for a more correct C++ design) - - what about thread cancelation ? Do we assume kdar will fork() rather than require a more complex mechanism to cancel a thread ? Cheers, Denis. Johnathan Burchill wrote: | On Saturday 30 October 2004 01:00, Johnathan Burchill wrote: | |>Hi Denis, |> |>I've decided it is time to port KDar over to the new libdar API3. Libdar |>installed without obvious problems. However, KDar's configure script |>chokes, and spits out the following log messages: |> |>configure:32503: checking dar/libdar.hpp usability |>configure:32515: g++ -c -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall |>-pedantic |>-W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi |>-D_XOPEN_SOURCE=500 |>-D_BSD_SOURCE -Wcast-align -Wconversion -DNDEBUG -DNO_DEBUG -O2 -O2 |>-pipe -march=a |>thlon-xp -mmmx -msse -m3dnow -fno-exceptions -fno-check-new -fexceptions |>-fexcepti |>ons -DQT_THREAD_SUPPORT -D_REENTRANT conftest.cc >&5 |>In file included from /usr/local/include/dar/storage.hpp:29, |> from /usr/local/include/dar/real_infinint.hpp:38, |> from /usr/local/include/dar/infinint.hpp:30, |> from /usr/local/include/dar/compressor.hpp:30, |> from /usr/local/include/dar/libdar.hpp:32, |> from conftest.cc:148: |>/usr/local/include/dar/erreurs.hpp: In constructor |> `libdar::Ememory::Ememory(const std::string&)': |>/usr/local/include/dar/erreurs.hpp:67: `gettext' undeclared (first use |>this function) |>/usr/local/include/dar/erreurs.hpp:67: (Each undeclared identifier is |>reported only once for each function it appears in.) |>configure:32521: $? = 1 |> |>I am not familiar with gettext, but it seems that the function should be |>declared somewhere. |> |>Any ideas? | | | I've just upgraded to Slackware 10, and the problem disappeared. There | might have been a glibc version problem or mismatch somewhere. | | Cheers, | JB | | |>Cheers, |>JB | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBhiHapC5CI8gYGlIRAtL8AJsFEvg12nous1lYzEVfZWkAgpWWCgCfUyGx VMPGVO1YnQWYccsMJjwjbl8= =aU4m -----END PGP SIGNATURE----- |