Eric Lemings wrote:
FYI. I'm also seeing this build failure on HP-UX as well:
I don't see this error on the head of trunk either with gcc 4.1.1
on Solaris or 4.1.2 on Linux. If you see the same problem on trunk
please open an issue for it mentioning the gcc version and build
type.
Martin
-----
...
"/work/stdcxx/branches/4.2.x.twister/include/functional", line 90: error
#2349: no operator "*" matches these operands
operand types are: const UserClass * const UserClass
return __x * __y;
^
detected during:
instantiation of "std::binary_function<_TypeT, _TypeT,
_TypeT>::result_type std::multiplies<_TypeT>::operator()(const
std::binary_function<_TypeT, _TypeT, _TypeT>::first_argument_type &,
const std::binary_function<_TypeT, _Ty
peT, _TypeT>::second_argument_type &) const [with _TypeT=UserClass]" at
line 360 of "/work/stdcxx/branches/4.2.x.twister/include/algorithm"
instantiation of "_OutputIter std::transform(_InputIter1,
_InputIter1, _InputIter2, _OutputIter, _BinaryOperation) [with
_InputIter1=UserClass *, _InputIter2=const UserClass *,
_OutputIter=UserClass *, _BinaryOperation=std::m
ultiplies<UserClass>]" at line 373 of
"/work/stdcxx/branches/4.2.x.twister/include/valarray"
instantiation of "std::valarray<_TypeT>
&std::valarray<_TypeT>::operator*=(const std::valarray<_TypeT> &) [with
_TypeT=UserClass]" at line 354 of
"/work/stdcxx/branches/4.2.x.twister/tests/numerics/26.valarr
ay.cassign.cpp"
instantiation of "void test_mul_assign(const T *, const char
*, const char *) [with T=UserClass]" at line 758 of
"/work/stdcxx/branches/4.2.x.twister/tests/numerics/26.valarray.cassign.
cpp"
instantiation of "void test_op_assign(const T *, const char
*) [with T=UserClass]" at line 818 of
"/work/stdcxx/branches/4.2.x.twister/tests/numerics/26.valarray.cassign.
cpp"
...
------
Brad.
________________________________
From: Eric Lemings
Sent: Thursday, March 13, 2008 12:23 PM
To: '[email protected]'
Subject: [gcc/Mac] build failure: 26.valarray.cassign
Encountered a build failure compiling the
26.valarray.cassign.cpp file. See attached output.
This look familliar to anyone? If not, I'll create a new Jira
issue for it.
Thanks,
Brad.