error #2266: "input_iterator_tag with aCC 6.15

[Dennis Handly]

>I am getting the following linking error while porting third party tool(ospace) from PA-RISC to IPF.

What does ospace do? I'm familiar with their C++ Standard Library. Is this what you are using it for? (The above -Ds indicates this maybe true.) If so, you'll have problems and need to compile with +nostl.

>Could you please let me know why I am getting the above error?

You need to start all over. Why are you using ospace when HP has it's own C++ Standard Library? If you don't use HP's, you are on your own and must use +nostl and then figure out what's missing.

I don't know why you are getting these unsats since they should all be defined in libstd_v2.

[Neel2]

Thanks again for your invaluable input.

I will try with the above flag and let you know the results.

Thanks,
Neel

[Neel2]

Hello,

Correct me If I am wrong?

If I build with -AA flag, then the build would be ANSI build, and if i use -AP flag then build be non-ansi?

Regards,
Neel

[Dennis Handly]

>If I build with -AA flag, then the build would be ANSI build, and if i use -AP flag then build be non-ansi?

Yes. But if you are using +nostl, it might not matter so much.

[Neel2]

Hi,

(Sorry, for going out of track)
Could you please let me know, how can i compile the following statement on PA-RISC
using the following conf:
aCC: HP ANSI C++ B3910B A.03.57
HP-UX B.11.11 U 9000/800 109092009 unlimited-user license

The statement is:
const o_double MAX = (std::numeric_limits::max)();


Currently I can compile the above statement using -AA, but i need to compile with the default on PA-RISC which is -AP, Could you please let me know how can modify the above statement in order to get compile with -AP.

I have gone thru the following FAQ's.
Can I use this in any way:
11. Can I write code that works for both?

Yes. Only with conditional compilation. And/or by using the following
namespace std:: construct:
namespace std {} using namespace std;
You can put this construct anywhere, as many times as you like. Or once at the beginning - as long it is before you reference any symbol that doesn't have the needed std::. And you can use it with -AP too.


Regards,
Neel

[Dennis Handly · Accepted solution]

You sked it in your other thread. I'll answer it there:
[broken link removed on <4/4/2017> by Mod]

[Neel2]

Ok.

Thank you.

[Neel2]

Hello,

>>I don't know why you are getting these unsats since they should all be defined in libstd_v2

Yes, If I explicitly provide -lstd_v2 while linking executable it does resolve the unstats.

Thanks for your hints/suggestions.

Kind regards,
Neel

[Neel2]

Got satisfied answers.