Re: [Discuss-gnuradio] Problem with gr-error-correcting-codes/src/lib/libecc

[Eric Blossom]

On Tue, Aug 01, 2006 at 11:41:10AM -0700, Johnathan Corgan wrote:
> I'm getting a compile time error with gr-error-correcting-codes in libecc:
> 
> code_convolutional_trellis.cc:293: error: no match for 'operator=' in
> 't_fb_generators_soai =
> ((code_convolutional_trellis*)this)->code_convolutional_trellis::d_code_feedback'
> /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/bits/vector.tcc:133:
> note: candidates are: std::vector<_Tp, _Alloc>& std::vector<_Tp,
> _Alloc>::operator=(const std::vector<_Tp, _Alloc>&) [with _Tp = unsigned
> int, _Alloc = std::allocator<unsigned int>]
> code_convolutional_trellis.cc:353: error: no match for 'operator=' in
> '((code_convolutional_trellis*)this)->code_convolutional_trellis::d_code_feedback
> = t_fb_generators_soai'
> /usr/lib/gcc/i486-linux-gnu/4.0.3/../../../../include/c++/4.0.3/bits/vector.tcc:133:
> note: candidates are: std::vector<_Tp, _Alloc>& std::vector<_Tp,
> _Alloc>::operator=(const std::vector<_Tp, _Alloc>&) [with _Tp = long
> unsigned int, _Alloc = std::allocator<long unsigned int>]
> 
> Then there are several more like this:
> 
> code_convolutional_trellis.cc: In member function 'void
> code_convolutional_trellis::create_trellis()':
> code_convolutional_trellis.cc:573: error: call of overloaded
> 'n2bs(memory_t&, size_t&)' is ambiguous
> ./mld/n2bs.h:27: note: candidates are: std::string n2bs(char, size_t)
> ./mld/n2bs.h:28: note:                 std::string n2bs(int, size_t)
> ./mld/n2bs.h:29: note:                 std::string n2bs(long int, size_t)
> ./mld/n2bs.h:30: note:                 std::string n2bs(size_t, size_t)
> ./mld/n2bs.h:31: note:                 std::string n2bs(long long int,
> size_t)
> 
> 
> If I 'make -k' it will continue and successfully compile and link
> everything else in libecc directory (encoder.o, decoder.o, and
> code_metrics.o all show up in .libs).
> 
> This is with latest CVS but it looks like the file date is July 20.
> 
> Might this be a problem with GCC 4.0.3?

Don't think so.  I get the same problem with gcc 4.0.2 on x86.  
It does work for me on x86-64 with g++ 3.3.5, but it's 64-bit.  The
ambiguity may be being caused by different widths for the different
types under different architectures.

Eric