That's a bit odd. If you are compiling for arm, you should not be including anything from the x86_64 lib tree.
Secondly you seem to be confusing the difference between a software package, and its contents. The package is libbluetooh-dev. It has headers, documentation and other files that are needed to compile a program that uses libbluetooth. The package libbluetooth3 contains the shared library: /usr/lib/arm-linux-gnueabihf/libbluetooth.so.3.xx.yy, so you should ask to link only with -lbluetooth
Thirdly: if you've installed the gcc cross-copmiler tools correctly, it should know how to find libm without any additional help from you. Consider the following very simple program
}In order to compile it, we need to include libm. On my X86-64 computer I do
gcc example.c -o example -lm to create an x86-64 executable program. To create an ARM version I do
gcc-arm7 example.c -o example-arm -lmI now have 2 versions of the example program, one for X86-64 and one for ARM e.g.
k5054@loaclhost $ file example example-arm
example: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=c5d319f4b896ad825b708ff73a248ed23f64489f, for GNU/Linux 3.2.0, not stripped
example-arm: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=1bc8369c7de09a7510c93c0bcab5824c6342d688, for GNU/Linux 3.2.0, not strippedAre you sure you've installed the cross compiler correctly and can produce simple programs (like example.c above or a basic hello world) that can run on the RPI?
Keep Calm and Carry On