[Home]

Summary:ASTERISK-14445: [patch] Building dahdi-linux-2.1.0.4 as cross-compilation works, but 2.2.0 fails with wrong architecture type
Reporter:Philip Prindeville (pprindeville)Labels:
Date Opened:2009-07-09 13:10:41Date Closed:2011-06-07 14:00:44
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/BuildSystem
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) dahdi-linux.log
( 1) dahdi-linux2.log
( 2) dahdi-linux-rm.patch
Description:Building 2.1.0.4 on FC9 (x86_64) for an i386 (i586 really) target works fine.

Updating to 2.2.0 fails:

make -C /home/philipp/kernel/build_i586/linux-2.6.27.26-astlinux SUBDIRS=/home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi DAHDI_INCLUDE=/home/philipp/kernel/build_i586/dahdi-linux-2.2.0/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m
make[2]: Entering directory `/home/philipp/kernel/build_i586/linux-2.6.27.26-astlinux'
 SHIPPED /home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_64.o
 LD [M]  /home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi/dahdi.o
 LD [M]  /home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi/dahdi_vpmadt032_loader.o
ld: Relocatable linking with relocations from format elf64-x86-64 (/home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_64.o) to format elf32-i386 (/home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi/dahdi_vpmadt032_loader.o) is not supported
make[3]: *** [/home/philipp/kernel/build_i586/dahdi-linux-2.2.0/drivers/dahdi/dahdi_vpmadt032_loader.o] Error 1


****** ADDITIONAL INFORMATION ******

Logs for both builds attached.
Comments:By: Philip Prindeville (pprindeville) 2009-07-09 13:11:15

First log is 2.1.0.4.
By: Philip Prindeville (pprindeville) 2009-07-09 13:11:45

Second log is 2.2.0.
By: Shaun Ruffell (sruffell) 2009-07-09 13:58:48

What if you try building like:

KRSC=/home/philipp/kernel/build_i586/linux-2.6.27.26-astlinux make ARCH=i386?
By: Philip Prindeville (pprindeville) 2009-07-11 12:47:39

That seems to have fixed it.  Also, attaching a fix for an extraneous (and avoidable) error message when building.
By: Philip Prindeville (pprindeville) 2009-07-11 17:41:23

Doh!  That latter issue is already reported as 15479.  Sorry.
By: Philip Prindeville (pprindeville) 2009-11-16 18:54:31.000-0600

Please close this out.  Explicitly naming the architecture (while ugly) is effective.