[Wave] FIx for Jamfile.v2
Hi ! The following patch corrects a typo in tools/wave/build/Jamfile.v2 which prevents wave to be built. It seems that the wave tool is broken because I get tons of errors frm cpp.cpp. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister StraÃe 15 * hunold@ive-mbh.de ! www.ive-mbh.de
Jürgen,
The following patch corrects a typo in tools/wave/build/Jamfile.v2 which prevents wave to be built. It seems that the wave tool is broken because I get tons of errors frm cpp.cpp.
Thanks for the patch! I've applied it to the CVS. What errors do you get? Which platform, which compiler? The Wave tool compiles fine for me (tm). Regards Hartmut
Yours,
Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * hunold@ive-mbh.de ! www.ive-mbh.de
Hi Hartmut ! Am Middeweken 19 April 2006, 00:45 schrieb Hartmut Kaiser:
Jürgen,
Thanks for the patch! I've applied it to the CVS. What errors do you get? Which platform, which compiler? The Wave tool compiles fine for me (tm).
I'm using SuSE-Linux 10.0 on AMD 64. g++ -v Using built-in specs. Target: x86_64-suse-linux Thread model: posix gcc version 4.0.2 20050901 (prerelease) (SUSE Linux) Please find a full backtrace attached. The first errors are easy to fix (missing includes) and then some lookup problems. The main problem seem to be a missing "operator&" for serialization of boost::filesystem::path. I get the same errors at home, using debian gcc-4.0.3. I don't have the time to look into the depths of boost::serialization to debug this... Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * hunold@ive-mbh.de ! www.ive-mbh.de
Jürgen,
Thanks for the patch! I've applied it to the CVS. What errors do you get? Which platform, which compiler? The Wave tool compiles fine for me (tm).
I'm using SuSE-Linux 10.0 on AMD 64.
g++ -v Using built-in specs. Target: x86_64-suse-linux Thread model: posix gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)
Please find a full backtrace attached. The first errors are easy to fix (missing includes) and then some lookup problems. The main problem seem to be a missing "operator&" for serialization of boost::filesystem::path.
I get the same errors at home, using debian gcc-4.0.3.
I don't have the time to look into the depths of boost::serialization to debug this...
Thanks! I hope to have it fixed now (it's in CVS). Could you please try it out and report back to me? Regards Hartmut
Yours,
Jürgen
-- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * hunold@ive-mbh.de ! www.ive-mbh.de
Hi Hartmut ! On Wednesday 19 April 2006 16:58, Hartmut Kaiser wrote:
Jürgen,
Thanks! I hope to have it fixed now (it's in CVS). Could you please try it out and report back to me?
Okay, it compiles with gcc-4.0.3 But with some gcc-specific warnings. ../../../boost/archive/basic_binary_iprimitive.hpp:87: warning: unused variable 'i' This local variable is used in an assert-statement, which is of course not visible in release mode. Is there any Boost makro to disable this warning ? And gcc complains "warning: the use of `tmpnam' is dangerous, better use `mkstemp'" in " In function `bool trace_macro_expansion<" A quick run with gcc-4.1 failed with ../../../boost/lexical_cast.hpp:167: error: no match for 'operator>>' in '((boost::detail::lexical_stream<cmd_line_util::include_paths, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
*)this)->boost::detail::lexical_stream<cmd_line_util::include_paths, std::basic_string<char, std::char_traits<char>, std::allocator<char> > ::stream >> output'
Full compiler output attached. Compiler: gcc version 4.0.3 (Debian 4.0.3-1) gcc version 4.1.0 (Debian 4.1.0-1) Yours. Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister StraÃe 15 * hunold@ive-mbh.de ! www.ive-mbh.de
Juergen Hunold wrote:
Thanks! I hope to have it fixed now (it's in CVS). Could you please try it out and report back to me?
Okay, it compiles with gcc-4.0.3 But with some gcc-specific warnings.
../../../boost/archive/basic_binary_iprimitive.hpp:87: warning: unused variable 'i'
This local variable is used in an assert-statement, which is of course not visible in release mode. Is there any Boost makro to disable this warning ?
That's outside of my control. I've CC'ed Robert who might be able to correct this.
And gcc complains "warning: the use of `tmpnam' is dangerous, better use `mkstemp'"
in " In function `bool trace_macro_expansion<"
Ok, will try to fix this.
A quick run with gcc-4.1 failed with
../../../boost/lexical_cast.hpp:167: error: no match for 'operator>>' in '((boost::detail::lexical_stream<cmd_line_util::include_paths, std::basic_string<char, std::char_traits<char>, std::allocator<char> >
*)this)->boost::detail::lexical_stream<cmd_line_util::include_paths, std::basic_string<char, std::char_traits<char>, std::allocator<char> > ::stream >> output'
That's outside of my control either. I'm not sure, who is responsible here, though. Thanks! Regards Hartmut
Full compiler output attached. Compiler:
gcc version 4.0.3 (Debian 4.0.3-1) gcc version 4.1.0 (Debian 4.1.0-1)
Yours.
Jürgen
-- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * hunold@ive-mbh.de ! www.ive-mbh.de
participants (3)
-
Hartmut Kaiser -
Juergen Hunold -
Jürgen Hunold