Compile error listing

[soccertl]

Is there a listing of what the compile errors mean? For example:

"hdb_log.c", line 163.22: 1506-046 (S) Syntax error.
"hdb_log.c", line 160.20: 1506-098 (E) Missing argument(s).
make: 1254-004 The error code from the last command is 1.

How do I find out what 1506-046 and 1506-098 mean?

Thanks for any help.

 

[Dan Henry]

Is there a listing of what the compile errors mean? For example:

"hdb_log.c", line 163.22: 1506-046 (S) Syntax error.
"hdb_log.c", line 160.20: 1506-098 (E) Missing argument(s).
make: 1254-004 The error code from the last command is 1.

How do I find out what 1506-046 and 1506-098 mean?

Presumably those error messages are excreted by your compiler. I'd
reach for the compiler manual first.

 

[Peter Nilsson]

No. The language standard only requires compilers to issue diagnostics
in specific cases, but a compiler can otherwise issue a diagnostic for
any
reason it likes. What those diagnostics say (and mean) is up to the
implementation. Specific implementation details are generally outside
the
scope of comp.lang.c.

Presumably they mean 'Syntax error' and 'Missing argument(s)'
respectively.

Presumably those error messages are excreted by your compiler. I'd
reach for the compiler manual first.

Or, if you want to save some time, just open "hdb_log.c" around lines
160
through 163 and check what the syntax error is.

If it's not actually your code, then almost certainly the code relies
on
compiler extensions and either you have failed to activate those
extensions,
or they don't exist with the compiler you're using.

 

[Jaspreet]

Is there a listing of what the compile errors mean? For example:

"hdb_log.c", line 163.22: 1506-046 (S) Syntax error.
"hdb_log.c", line 160.20: 1506-098 (E) Missing argument(s).
make: 1254-004 The error code from the last command is 1.

How do I find out what 1506-046 and 1506-098 mean?

Thanks for any help.

Refer to your compiler manual. Posting a minimal code snippet would
help us all.

 

[Keith Thompson]

Refer to your compiler manual. Posting a minimal code snippet would
help us all.

A minimal code snippet wouldn't help us figure out what 1506-046 and
1506-098 mean.

 

[CBFalconer]

Presumably those error messages are excreted by your compiler.
I'd reach for the compiler manual first.

The verbiage hung on the rear end of the error messages might give
the OP a clue.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

 

[Jaspreet]

A minimal code snippet wouldn't help us figure out what 1506-046 and
1506-098 mean.

If the buggy code is posted by the OP that would atleast help resolve
the errors.

 

[Martin Ambuhl]

Is there a listing of what the compile errors mean? For example:

"hdb_log.c", line 163.22: 1506-046 (S) Syntax error.

This diagnostic suggests that you have a syntax error detected on line
163.22 (although it might have occurred earlier & was not detected until
this line).

"hdb_log.c", line 160.20: 1506-098 (E) Missing argument(s).

This diagnostic suggests that you have at least one missing argument on
line 160.20.

make: 1254-004 The error code from the last command is 1.

This seems to be a diagnostic from 'make', which is not in any way part
of C and is off-topic.

How do I find out what 1506-046 and 1506-098 mean?

In your implementation's documentation.

Thanks for any help.

Learn to help yourself. Until you can master the rather easy task of
checking your implementation's documentation you will be lost.

 

[Mark McIntyre]

Is there a listing of what the compile errors mean? For example:

"hdb_log.c", line 163.22: 1506-046 (S) Syntax error.
"hdb_log.c", line 160.20: 1506-098 (E) Missing argument(s).
make: 1254-004 The error code from the last command is 1.

How do I find out what 1506-046 and 1506-098 mean?

I'd start in the usual way, by looking at the indicated lines of code,
and trying to fix up the error. I strongly suspect that you will learn
what the error codes mean (though the last two words of each error
message are a pretty good indication...)
Mark McIntyre

 

[soccertl]

Thanks for all the replies. I already know what the problem is and
fixed it in code. I didn't need help with that. I was just curious if
the numbers suggested anything more specific or different than the text
that was printed out. Apparently they don't so I won't pursue it any
further.

Thanks again.

 

[Walter Roberson]

Presumably they mean 'Syntax error' and 'Missing argument(s)'
respectively.

Semantic quibble:

1506-046 and 1506-098 and 1254-004 are probably error-message keys,
which might or might not have internal structure in some terms of
reference.

One is probably best off assuming that there is no internal structure
to them, or that at most the structure is that "the part before the
dash is a magic number that the system implementors reserved for that
particular application, and the part after the dash is the specific key
for that message number within that application."

The semantic quibble is that I would say that the numbers do not
"mean" those particular messages, but rather that for that
particular version of the software, they "indicate" conditions that
correspond to those messages.

For example, if the implementation had a big table of messages,
then the 46th message in that table might be for "Syntax error"
(in that version.) If the implementation happened to print the offset
into the message table as well as the message text, then one might
come to think that the 46 -meant- "Syntax error", but really the 46
was happenstance and the content was what was important.


What I would -suspect- is that those strings 1506-046 and 1506-098 and
1254-004 are keys into an internationalization message table (i18n);
and that the implementation does not have things like
"Syntax error" hard-coded, and instead supplies the key 1506-046
to a message lookup routine which examines the locale to find the
database of messages in the user's language, and looks the key up in
there to find the corresponding text.

If my suspicion is right, then the numbers really don't "mean" anything
and are just arbitrary labels that are used in common by the
implementation and the message tables.

 

[Kenneth Brody]

Thanks for all the replies. I already know what the problem is and
fixed it in code. I didn't need help with that. I was just curious if
the numbers suggested anything more specific or different than the text
that was printed out. Apparently they don't so I won't pursue it any
further.

[Insert obligatory reference to "how to properly use Google's broken
Usenet quoting interface" here.]

Nobody said that they "don't" mean anything. It may be that they mean
quite a lot to your particular compiler, but the only way to find out
would be to look at your specific compiler's documentation, because
that's the only place that could tell you what, if anything, they mean.

--
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody | www.hvcomputer.com | |
| kenbrody/at\spamcop.net | www.fptech.com | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+
Don't e-mail me at: <mailto:[email protected]>

 

[Keith Thompson]

Thanks for all the replies. I already know what the problem is and
fixed it in code. I didn't need help with that. I was just curious if
the numbers suggested anything more specific or different than the text
that was printed out. Apparently they don't so I won't pursue it any
further.

Please read <http://cfaj.freeshell.org/google/>. Even if nothing in
the previous article is directly relevant to your followup, quoting a
line or two will avoid this annoying reminder.

We don't know whether the numeric codes mean anything. They certainly
don't mean anything in standard C, but they may be significant in your
environment. Since they're produced by your compiler, the
documentation for your compiler should tell you something more about
them. (On some systems, there's a separate command that takes an
error code and gives you a detailed explanation of what it means.)