Bug 415516

Summary: Can't cross compile on openwrt
Product: [Developer tools] valgrind Reporter: wei <kevin_jia>
Component: vexAssignee: Julian Seward <jseward>
Status: CONFIRMED ---    
Severity: normal CC: arikalo, mips32r2
Priority: NOR    
Version First Reported In: 3.15 SVN   
Target Milestone: ---   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: config.log
Fix OpenWRT build [WIP]

Description wei 2019-12-24 08:25:12 UTC 
SUMMARY


STEPS TO REPRODUCE
1. cd valgrind-3.15.0
2. ./configure --host=mipsel-openwrt-linux CC=/root/Desktop/CC_TOOLS/bin/mipsel-openwrt-linux-gcc CPP=/root/Desktop/CC_TOOLS/bin/mipsel-openwrt-linux-cpp CXX=/root/Desktop/CC_TOOLS/bin/mipsel-openwrt-linux-g++  LD=/root/Desktop/CC_TOOLS/bin/mipsel-openwrt-linux-ld AR=/root/Desktop/CC_TOOLS/bin/mipsel-openwrt-linux-ar --prefix=/home/wei/valgrind 
3. make

OBSERVED RESULT
/tmp/ccrjZn2z.s:4568: Error: unrecognized opcode `cfcmsa $t0,$1'
/tmp/ccrjZn2z.s:4569: Error: unrecognized opcode `ctcmsa $1,$4'
/tmp/ccrjZn2z.s:4570: Error: unrecognized opcode `ld.b $w24,0($2)'
/tmp/ccrjZn2z.s:4571: Error: unrecognized opcode `ld.b $w26,0($3)'
/tmp/ccrjZn2z.s:4572: Error: unrecognized opcode `fadd.w $w24,$w24,$w26'
/tmp/ccrjZn2z.s:4573: Error: unrecognized opcode `cfcmsa $2,$1'
/tmp/ccrjZn2z.s:4574: Error: unrecognized opcode `ctcmsa $1,$t0'
/tmp/ccrjZn2z.s:4593: Warning: tried to set unrecognized symbol: msa

/tmp/ccrjZn2z.s:4595: Error: unrecognized opcode `cfcmsa $t0,$1'
/tmp/ccrjZn2z.s:4596: Error: unrecognized opcode `ctcmsa $1,$4'
/tmp/ccrjZn2z.s:4597: Error: unrecognized opcode `ld.b $w24,0($2)'
/tmp/ccrjZn2z.s:4598: Error: unrecognized opcode `ffint_u.d $w24,$w24'
/tmp/ccrjZn2z.s:4599: Error: unrecognized opcode `cfcmsa $2,$1'
/tmp/ccrjZn2z.s:4600: Error: unrecognized opcode `ctcmsa $1,$t0'
/tmp/ccrjZn2z.s:4642: Warning: tried to set unrecognized symbol: msa

/tmp/ccrjZn2z.s:4644: Error: unrecognized opcode `cfcmsa $2,$0'
make[3]: *** [priv/libvex_mips32_linux_a-guest_mips_helpers.o] Error 1
make[3]: Leaving directory `/home/wei/valgrind-3.15.0/VEX'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/wei/valgrind-3.15.0/VEX'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/wei/valgrind-3.15.0'
make: *** [all] Error 2


EXPECTED RESULT
make finish

SOFTWARE/OS VERSIONS valgrind-3.15.0
Windows: Vmware ubuntu 14.04LTS
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: openwrt chaos calmer
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
mipsel-openwrt-linux-gcc --version
mipsel-openwrt-linux-uclibc-gcc.bin (OpenWrt/Linaro GCC 4.8-2014.04 r47072) 4.8.3
Comment 1 wei 2019-12-24 08:31:10 UTC 
Created attachment 124683 [details]
config.log
Comment 2 wei 2019-12-24 08:44:06 UTC 
OpenWrt GCC 8.3.0 r11655-a283b17
update GCC version can solve it.
Comment 3 Aleksandar Rikalo 2020-02-24 13:45:01 UTC 
Created attachment 126374 [details]
Fix OpenWRT build [WIP]

Hi, this patch fixes the "msa" issue with "mipsel-openwrt-linux-uclibc-gcc.bin (OpenWrt/Linaro GCC 4.8-2014.04 r47072) 4.8.3"
Please let me know is it helpful.

However, there is another problem during linkage of vgdb:

/work/toolchain/iDetect-839d28effb806ce37c6c85b0da3de22bd6255450/OpenWrt-Toolchain-ramips-mt7688_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/toolchain-mipsel_24kec+dsp_gcc-4.8-linaro_uClibc-0.9.33.2/bin/../lib/gcc/mipsel-openwrt-linux-uclibc/4.8.3/../../../../mipsel-openwrt-linux-uclibc/lib/libpthread.so.0: undefined reference to `dlopen'
/work/toolchain/iDetect-839d28effb806ce37c6c85b0da3de22bd6255450/OpenWrt-Toolchain-ramips-mt7688_gcc-4.8-linaro_uClibc-0.9.33.2.Linux-x86_64/toolchain-mipsel_24kec+dsp_gcc-4.8-linaro_uClibc-0.9.33.2/bin/../lib/gcc/mipsel-openwrt-linux-uclibc/4.8.3/../../../../mipsel-openwrt-linux-uclibc/lib/libpthread.so.0: undefined reference to `dlsym'
collect2: error: ld returned 1 exit status
Makefile:2883: recipe for target 'vgdb' failed

It seems that dlopen/dlsym functions are missing in provided version of uClibc. Have you ever encountered this situation (using this particular version of toolchain) ?

Best wishes,
Aleksandar
Comment 4 Petar Jovanovic 2020-02-25 15:34:15 UTC 
I would suggest that this issue gets resolved by upgrading toolchain version, if possible.