undefined symbol about ptos HOT 5 CLOSED

On Sat, Aug 4, 2018, 12:50 Paul Wratt ***@***.***> wrote: ok, almost there, now I am getting: `` Is the following RPi specific or GCC specific: ELF_LIB_REF(__mulsi3) ELF_LIB_REF(__divsi3) ELF_LIB_REF(__modsi3) ELF_LIB_REF(__udivsi3) ELF_LIB_REF(__umodsi3) ELF_LIB_REF(__aeabi_idiv) ELF_LIB_REF(__aeabi_idivmod) ELF_LIB_REF(__aeabi_udiv) ELF_LIB_REF(__aeabi_uidiv) ELF_LIB_REF(__aeabi_udivmod) ELF_LIB_REF(__aeabi_uidivmod) "i" means integer maths here doesn't it? why are they hard coded? how can these symbols be present in assembled code if they are NOT present in the libs they reference (libgcc.a in this case). when I do arm-none-eabi-nm /usr/lib/gcc/arm-none-eabi/4.8/libgcc.a | grep "__mul" I get: 00000000 T __muldf3 00000000 T __mulsf3 00000000 T __muldi3 00000000 T __mulvsi3 00000000 T __mulvdi3 00000000 T __mulsc3 00000000 T __muldc3 and when I do arm-none-eabi-nm /usr/lib/gcc/arm-none-eabi/4.8/libgcc.a | grep "_muls" I get: 00000000 T __mulsf3 _mulsc3.o: 00000000 T __mulsc3 00000000 T __gnu_mulsq3 00000000 T __gnu_mulsa3 same with fpu/libgcc.a. by the way on RPi this usually indicates the need for -lm and a specific -L directory. but I also notice there are no "i" references there either, except __mulvsi3 & __mulvdi3. however all the "aeabi"+"idiv" references seem to be present I will try non-cross with gcc-6.1.0 tomorrow, as I read in a baremetal tut that you dont *need* arm-none-eabi when compiling on the actual hardware (just static linking). actually I just checked 6.1.0 with /usr/local/gcc-6.1.0/bin/gcc-nm-6.1.0 /usr/local/gcc-6.1.0/lib/gcc/arm-linux-gnueabihf/6.1.0/libgcc.a | grep muls and I get the exact same as above, also with GCC 4.9, so it looks like some of those symbols are not present on actual Raspbian/Debian for Pi. I could probably #if defined(RPI) & !defined(QEMU) the actual values in, presuming this is the right thing to do (I dont have a m68k-atari-mint on any Raspbian distro to triple check) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADT4scKSOcvqqbbHuFxdRAboqeYCnyFtks5uNXxjgaJpZM4Vu8vV> .