Hi Florian, I think you are right: the point is the toolchain. At the moment we could not release anything. The toolchain targets a normal glibc, I was expecting buildroot would interpert it, or at least give the oportunity to use different libc than uclibc when using an external toolchain, as when building the toolchain (using openwrt buildroot) one can choose between glibc, eglibc and uclibc. Am I wrong?
thanks once again! On Wed, Feb 20, 2013 at 11:47 AM, Florian Fainelli <[email protected]>wrote: > Hello Alberich, > > > On 02/19/2013 04:06 PM, Alberich de megres wrote: > >> Hi FLorian, >> >> The board contains a Broadcom SoC similar to the one in the raspberry pi >> (not the same), we have a kernel working for it, but when tryingo to >> port the openwrt all blowed up. >> >> For the moment I did: (it is a work in progress) >> Created target/linux/hardfp/Makefile >> Created target/linux/hardfp/profiles/1**00-hardfp.mk<http://100-hardfp.mk>< >> http://100-hardfp.mk> >> >> Added a valid .config named config-3.6 (copied it after configuring a >> > > [snip] > > > >> DEFAULT_PACKAGES += kmod-usb-hid >> CFLAGS:=-mfloat-abi=hard -mfpu=vfp -mtune=arm1176jzf-s -march=armv6zk >> > > Ok this is good, I used basically the same CFLAGS on realview to test > building with a hard-float ABI in mind. > > > #KBUILD_CFLAGS:=${CFLAGS} >> #KBUILD_CFLAGS:= >> >> KERNELNAME:="Image_ubp" >> >> $(eval $(call BuildTarget)) >> >> ------------------ >> After this, I'm using an external tool chain, and I'm pointing to an own >> kernel git repo. >> In the openwrt menuconfig, enables the Advanced configuration option >> >> Enter git repo to clone: i'm using our own >> target options >> |-> target optimizations: -O2 -pipe -mfloat-abi=hard -mfpu=vfp >> -mtune=arm1176jzf-s -march=armv6zk >> > > This is not strictly required but does not conflict with what you want to > do. > > > >> In Use external toolchain: >> edited all options except the last 3 ( program path, toolchain include >> path and library path) >> > > Ok, I think the issue is that you are actually using an external toolchain > while I am using the toolchain built by OpenWrt. Can you point me at your > toolchain (if public) so I can try to fix the issues? Is your toolchain > built to target uClibc as libc as well? > > Thanks! > -- > Florian > >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
