Re: =mcpu=cortex-a7 buildlworld (for example) vs. __aeabi_uidiv use in ports from pkg

On Thu, 2017-01-26 at 02:10 -0800, Mark Millard wrote: > If I buildworld buildkernel for arm.armv6 with the likes of: > > CFLAGS+= =mcpu=cortex-a7 > CXXFLAGS+= =mcpu=cortex-a7 > CPPFLAGS+= =mcpu=cortex-a7 > > (say for targeting a bpim3 or rpi2) then what package > installs for that context tends

=mcpu=cortex-a7 buildlworld (for example) vs. __aeabi_uidiv use in ports from pkg

If I buildworld buildkernel for arm.armv6 with the likes of: CFLAGS+= =mcpu=cortex-a7 CXXFLAGS+= =mcpu=cortex-a7 CPPFLAGS+= =mcpu=cortex-a7 (say for targeting a bpim3 or rpi2) then what package installs for that context tends to report: Undefined symbol "__aeabi_uidiv" In other words __aeabi_ui