Hi All, I have a question regarding some small differences in the n3xx tool chain installation flow. Mainly, I see musleabi replace gnueabi in a few places. I am checking to see if this will cause a subtle issue down the line.
I followed the flow in the 'Obtaining an SDK' and 'SDK Usage' from https://files.ettus.com/manual/page_usrp_n3xx.html#n3xx_fsbuild to get the cross compile toolchain setup. I notice the extracted toolchain has some differences than what is listed in the guide. For example the environment setup script is 'environment-setup-cortexa9t2hf-neon-oe-linux-musleabi' instead of 'environment-setup-armv7ahf-vfp-neon-oe-linux-gnueabi'. 'echo $CC' on my machine gives below arm-oe-linux-musleabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 -mmusl --sysroot=/opt/oe/sysroots/cortexa9t2hf-neon-oe-linux-musleabi and '$CC -dumpmachine' prints out arm-oe-linux-gnueabi. On a N310, I run 'gcc -dumpmachine' and 'get arm-oe-linux-musleabi' instead of arm-oe-linux-gnueabi. I was able to do a basic hello world cross-compile and run on the N310 without an issue. Thanks Colby
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
