[Home]

Summary:ASTERISK-30122: GCC error when compiling Asterisk 18.13.0 with developer tools support
Reporter:Samuel Rey (goodcrossing)Labels:
Date Opened:2022-07-03 14:36:50Date Closed:2022-07-03 17:25:55
Priority:MinorRegression?Yes
Status:Closed/CompleteComponents:Tests/testsuite
Versions:18.13.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Raspberry Pi 3B+ running Raspbian 11 (Linux kernel 5.10.103-v7+)Attachments:
Description:When compiling Asterisk 18.13.0, with developer testsuite, the following GCC error is printed, and compilation halts:
{noformat}
[CCi] test_mwi.i -> test_mwi.o
test_mwi.c: In function 'mailbox_to_num':
test_mwi.c:73:27: error: passing argument 2 of 'ast_str_to_umax' from incompatible pointer type [-Werror=incompatible-pointer-types]
  73 |  if (ast_str_to_umax(++p, num)) {
     |                           ^~~
     |                           |
     |                           size_t * {aka unsigned int *}
In file included from test_mwi.c:27:
/usr/src/asterisk-18.13.0/include/asterisk/conversions.h:134:49: note: expected 'uintmax_t *' {aka 'long long unsigned int *'} but argument is of type 'size_t *' {aka 'unsigned int *'}
 134 | int ast_str_to_umax(const char *str, uintmax_t *res);
     |                                      ~~~~~~~~~~~^~~
cc1: all warnings being treated as errors
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2022-07-03 14:36:51.683-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.
By: Asterisk Team (asteriskteam) 2022-07-03 14:36:52.291-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Samuel Rey (goodcrossing) 2022-07-03 17:25:55.698-0500

Caused by third-party patch