| Summary: | DAHLIN-00292: vpmadt032 does not build/install correctly | ||||
| Reporter: | Richard Miller (ulogic) | Labels: | |||
| Date Opened: | 2012-05-21 07:08:05 | Date Closed: | 2012-05-23 11:40:42 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | wctdm24xxp | ||
| Versions: | 2.5.0.2 2.6.0 2.6.1 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | CentOS 6.2 x86_64, VPMADT032 | Attachments: | |||
| Description: | make install gives the following warning, but it actually is an error WARNING: could not find /usr/src/dahdi-linux-2.6.1/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_64.o.cmd for /usr/src/dahdi-linux-2.6.1/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_64.o The file it is looking for is drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_64.o.cmd However there is a file called drivers/dahdi/vpmadt032_loader/.dahdi_vpmadt032_loader.o.cmd If i copy the file .dahdi_vpmadt032_loader.o.cmd to .vpmadt032_x86_64.o.cmd, then when I do a make install, there are three additional lines of output CC /usr/src/dahdi-linux-2.6.1/drivers/dahdi/dahdi_vpmadt032_loader.mod.o LD [M] /usr/src/dahdi-linux-2.6.1/drivers/dahdi/dahdi_vpmadt032_loader.ko.unsigned NO SIGN [M] /usr/src/dahdi-linux-2.6.1/drivers/dahdi/dahdi_vpmadt032_loader.ko I was hoping to be able to submit a patch, but I couldn't find where in the build process the file was being generated. Please let me know where the change needs to be made. | ||||
| Comments: | By: Shaun Ruffell (sruffell) 2012-05-21 13:42:13.732-0500 This is only a warning and should not cause you any problems in operation. The problem is that the linker is looking for the .cmd file, which the compiler produces when creating the .o file. Since dahdi_vpmadt032_loader.o is provided in a binary format (since Digium does not have permission to distribute the firmware for the VPMADT032 in the clear) there is no .cmd file that would match with the compiler used to build the rest of DAHDI. The real question would be how to tell the linker to not worry about the .cmd file for that single .o file. If you ignore that warning, do you have any problems installing / running the binaries you compiled? By: Richard Miller (ulogic) 2012-05-23 10:32:40.412-0500 dmesg shows wctdm24xxp 0000:05:01.0: Booting VPMADT032 wctdm24xxp 0000:05:01.0: VPM present and operational (Firmware version 125) "service dahdi status" shows ### Span 2: WCTDM/0 "Wildcard TDM410P" (MASTER) 5 FXO FXSKS (EC: VPMADT032 - INACTIVE) 6 FXO FXSKS (EC: VPMADT032 - INACTIVE) 7 FXO FXSKS (EC: VPMADT032 - INACTIVE) 8 FXO FXSKS (EC: VPMADT032 - INACTIVE) It does appear to be working correctly, so this issue can be closed. By: Shaun Ruffell (sruffell) 2012-05-23 11:40:42.267-0500 Sounds good. | ||||