pendiala jaipal wrote:
Hi all,

i tried to build apache standard library ( stdcxx-4.2.1) on HPUX(11iv2) with 
acc 3.80.
I am getting these errors.

The error you pasted below is a future error that can be suppressed
via aCC's +W229 option. But unless these errors are also affecting
your programs I wouldn't be too concerned with them. The test is
probably buggy and needs to be fixed. There are a number of such
tests in our test suite and we've been working on cleaning them
up but we have ways to go.

FYI: You can see the test results on available platforms on this
page:

    http://stdcxx.apache.org/builds/4.2.1/

I don't see 17.extensions.cpp failing with either aCC 3.74 or with
6.16 but I do see similar errors on the 4.2.x branch:

  http://stdcxx.apache.org/builds/4.2.x/

It's possible that the 4.2.1 results are slightly out of date and
that a late change to the 4.2.1 branch might be responsible for
these errors. We'll need to investigate what caused the regression.
I opened a new issue to track this problem so feel free to subscribe
to it if you'd like to keep track of our progress on it.

  https://issues.apache.org/jira/browse/STDCXX-973

Martin


i used gmake CONFIG=acc.config
-----------------------------------------------------------------------------------------------------------------------

Error (future) 229: "/home/jaipal/Stdcxx/stdcxx-4.2.1/tests/intro/17.extensions.cpp", line 377 # "Ambiguous overloaded function call; a function match was not found that was strictly best for ALL arguments. Two functions that matched best for some arguments (but not all) were "std::istreambuf_iterator<char,std::char_traits<char> > std::num_get<char,std::istreambuf_iterator<char,std::char_traits<char> > >::get(std::istreambuf_iterator<char,std::char_traits<char> >,std::istreambuf_iterator<char,std::char_traits<char> >,std::ios_base &,__rw::__rw_iostate &,long double &) const" ["/home/jaipal/Stdcxx/stdcxx-4.2.1/include/loc/_num_get.h", line 124] and "std::istreambuf_iterator<char,std::char_traits<char> > std::num_get<char,std::istreambuf_iterator<char,std::char_traits<char> > >::get(std::istreambuf_iterator<char,std::char_traits<char> >,std::istreambuf_iterator<char,std::char_traits<char> >,std::ios_base &,__rw::__rw_iostate &,double &) const" ["/home/jaipal/Stdcxx/stdcxx-4.2.1/include/loc/_num_get.h", line 116]." Choosing "std::istreambuf_iterator<char,std::char_traits<char> > std::num_get<char,std::istreambuf_iterator<char,std::char_traits<char> > >::get(std::istreambuf_iterator<char,std::char_traits<char> >,std::istreambuf_iterator<char,std::char_traits<char> >,std::ios_base &,__rw::__rw_iostate &,long double &) const" ["/home/jaipal/Stdcxx/stdcxx-4.2.1/include/loc/_num_get.h", line 124] for resolving ambiguity.
        Warning:        2 future errors were detected and ignored. Add a '+p' 
option to detect and fix them before               they become fatal errors in 
a future release. Behavior of this ill-formed program is not guaranteed to 
match           that of a well-formed program

-----------------------------------------------------------------------------------------------------------------


Thanks in Advance,
Jaipal P.




Reply via email to