aCC error codes

[Dee Jacobs]

Is there a link to the manual of error codes for aCC?

[Steven E. Protter]

Shalom,

In there somewhere.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02019762/c02019762.pdf

SEP

[Dennis Handly · Accepted solution]

>Is there a link to the manual of error codes for aCC?

Error messages? What version of aC++ are you using?
For aCC6 there is "+Wv####" for select messages.
You can also look at /opt/aCC/lib/nls/msg/C/ecc.cat & ecc.msgs
And from HP Code Advisor:
http://h21007.www2.hp.com/portal/download/files/unprot/codeadvisor/Diagnosticdocumentation.pdf

>SEP: In there somewhere.

That's ACC, not aC++. We tried to make them give up on the TLA but they were first. :-(

[Dee Jacobs]

Thanks Dennis,
The cadvise will probably help when I get to that soon. Still trying to port my "c" application. Just for grins, can you lead me further on this example from my build.

"../include/navfns.h", line 57: error #2018: expected a ")"
extern double magnetic(double true, double variation);
^
The ecc.msgs only tells me the same as the error above. I suspect that's where they got the message in the make.

[Dennis Handly]

>The cadvise will probably help when I get to that soon.

They have the same messages and have cause text.

>navfns.h, line 57: error #2018: expected a ")"
extern double magnetic(double true, double variation);

You need to provide some lines before and after line 57 in navfns.h. It could be some evil macro that causing the problem.

>The ecc.msgs only tells me the same as the error above.

Unfortunately. Only aCC3 had some cause and action text.

[Dee Jacobs]

The error occurs in a list of externs in the .h file. They all seem to work except this one. This uses the word "true" which is indicated in the error message with the "^" character.

This compiles OK with cc_bundled.

Did I tread upon a reserved word list here? Something different in aCC?

Some surrounding code here (line four is the problem line):

extern double heading(xcoord * from, xcoord * to);
extern double kias_to_ktas(double kias, double altitude, double celsius);
extern double mach_to_ktas(double mach, double celsius);
extern double magnetic(double true, double variation);
extern double magnitude(xcoord * a);
extern double quickdist(double lat1, double lon1, double lat2, double lon2);
extern void radial_distance(xcoord * from, double heading, double dist, xcoo
rd * result);

Thanks for your assistance.

[Dennis Handly]

>This uses the word "true" which is indicated in the error message with the "^" character.

Ah, we can't see that in the forums. You need to use words to describe that.

>This compiles OK with cc_bundled. Did I tread upon a reserved word list here?

Yes, true is a C++ keyword but not in C.
Why don't you use cc vs aCC to compile? Otherwise you'll have to port your C application to C++.

[Dee Jacobs]

Dennis,
Thanks again for your reply.

We got aCC because cc does not permit the -g switch: therefore no debug. We will need the debug to complete this port, so we joined AllianceOne to get aCC.

I am in process of removing the compile bugs. aCC seems to be much pickier that cc. I'll just proceed through the list.

I was able to avoid the problem we were discussing. There was an unnecessary .h file inclusion there.

Good day,and thanks.

[Dee Jacobs]

See previous message.

[Dennis Handly]

>We got aCC because cc does not permit the -g switch: therefore no debug. We will need the debug to complete this port, so we joined AllianceOne to get aCC.

If you get aC++, you should get both a C and C++ compiler. It should be in /opt/aCC/bin/cc. What version do you have installed? The latest patch is A.06.25.01.

If you have the latter, then you should invoke that or make sure the link in /usr/bin/cc points to it.

You can always use "aCC -AC99" to switch to C99 mode.

>aCC seems to be much pickier that cc.

Of course.