Re: problem compiling KDar with libdar CVS

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

-- 
Johnathan K. Burchill, Ph.D.
Department of Physics and Astronomy
University of Calgary
2500 University Drive N.W.
Calgary, AB T2N 1N4
Canada

(403) 217-4286
[email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQBBhZKnrXMSOtiWrO4RAmH5AJ0dVFXcSM3NVTr4bYCjdwpayeDeXQCgtlH3
9G51IJs+Fnop8TkAjzuVc0U=
=bPJo
-----END PGP SIGNATURE-----