Summary: | ASTERISK-30108: zaptel compile error which says "cannot find autoconf.h" | ||
Reporter: | yongsoo Park (dooggy) | Labels: | |
Date Opened: | 2022-06-13 02:58:03 | Date Closed: | 2022-06-13 02:58:04 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_zapateller |
Versions: | 18.12.0 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | CentOs 7(Kernel version: 4.9.317) on VMware Workstation 16 Player Zaptel-1.4.12.1 | Attachments: | |
Description: | I built linux-4.9.317 from source code and wanted to install zaptel and asterisk on top of it.
First of all, I followed the exact steps described in guide book at Zaptel source directory. {code:xml} make clean ./configure make menuselect {code} When I tried to build Zaptel using "make", I got the following error {code:xml} CC [M] /usr/src/kernels/zaptel-1.4.12.1/kernel/pciradio.o In file included from /usr/src/kernels/zaptel-1.4.12.1/kernel/zaptel.h:39:0, from /usr/src/kernels/zaptel-1.4.12.1/kernel/pciradio.c:56: /usr/src/kernels/zaptel-1.4.12.1/kernel/zconfig.h:26:28: fatal error: linux/autoconf.h: No such file or directory #include <linux/autoconf.h> {code} I executed {code:xml} sudo yum install kernel-devel {code} to get {code:xml} Package kernel-devel-3.10.0-1160.66.1.el7.x86_64 already installed and latest version Nothing to do {code} and executed {code:xml} sudo yum install kernel-headers {code} to get {code:xml} Package kernel-headers-3.10.0-1160.66.1.el7.x86_64 already installed and latest version Nothing to do {code} I booted centOS at linux version "3.10.0-1160.66.1.el7.x86 64" and repeated the procedure again to see what difference it makes. But no diffrence!! Someone said that I needed to install kernel-sources, but I don't know what "installing kernel-souces" means. Please help me to get out of this headache!!! Many thanks in advance!!! | ||
Comments: | By: Asterisk Team (asteriskteam) 2022-06-13 02:58:04.369-0500 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2022-06-13 02:58:05.139-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/]. |