dar cvs compile fails with gcc-3.2.2

Johnathan Burchill <[email protected]>
Newsgroups gmane.comp.sysutils.backup.dar.general
Organization Department of Physics and Astronomy, University of Calgary
Message-ID <[email protected]>
Hi folks,

I am interested in making a qt frontend to dar. Obviously it will be more 
efficient using the library, rather than calling the command-line 
versions. Is anyone working on this?

Running gcc-3.2.2 I get compile errors in libdar.
The problem seems to be with the answer_callback code:
cannot pass objects of non-POD type `struct
shows up on lines with "user_interaction_warning".

I don't understand the parse errors before '&' token either.

Any ideas?

Cheers,
Johnathan

g++ -DHAVE_CONFIG_H -I. -I. -I../.. -O -MT filtre.lo -MD -MP -MF 
.deps/filtre.Tpo -c filtre.cpp  -fPIC
In file included from filtre.cpp:28:
user_interaction.hpp:45: parse error before `&' token
user_interaction.hpp:46: parse error before `&' token
user_interaction.hpp:51: parse error before `&' token
user_interaction.hpp:52: parse error before `&' token
filtre.cpp: In function `void libdar::filtre_restore(const libdar::mask&, 
const
   libdar::mask&, libdar::catalogue&, bool, const libdar::path&, bool, 
bool,
   bool, libdar::statistics&, bool, bool, bool, bool, bool, const
   libdar::infinint&)':
filtre.cpp:259: cannot pass objects of non-POD type `struct
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >'
   through `...'
filtre.cpp:263: cannot pass objects of non-POD type `struct
   std::basic_string<char, std::char_traits<char>, std::allocator<char> >'
   through `...'

etc...
-- 
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]



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.