Am 20.03.2012 21:57, schrieb davidMbrooke: > On Mon, 2012-03-19 at 22:56 +0000, davidMbrooke wrote: >> On Sun, 2012-03-18 at 23:59 +0200, Andrew wrote: >> > 18.03.2012 19:44, davidMbrooke пишет: >> > > >> > > I'm also thinking about what the "ARCH" arguments to buildtool.pl and >> > > buildpacket.pl should look like. Maybe we just use the GCC "target >> > > triplet" syntax, so e.g. >> > > i486-pc-linux-uclibc for the Bering-uClibc 4.x platform >> > > armv6-unknown-linux-uclibc for the Raspberry pi >> > > >> > > In other words, "buildtool.pl --target=i486-pc-linux-uclibc build ..." >> > > rather than "buildtool.pl --arch=i386 build ..." >> > > >> > > Thoughts? >> > > >> > > David >> > AFAIK there is no difference between '-pc-linux-uclibc' and >> > '-unknown-linux-uclibc' suffixes, and IMHO it'll be safe to use >> > i486-unknown-linux-uclibc arch. >> >> Thanks Andrew. I therefore propose to identify the different toolchains >> with "GNU_TARGET_NAME" strings like i486-unknown-linux-uclibc, instead >> of "ARCH" strings like i386. >> I will add a "-t toolchain" argument to buildtool.pl and default this to >> i486-unknown-linux-uclibc so as to preserve the current behaviour. >> >> I have these changes working in my development environment now (plus a >> few other changes to prepare for non-x86 platforms) but I want to review >> those again before adding to Git (hopefully tomorrow). >> >> david > > OK, changes now pushed to the SourceForge Git. Hopefully I have > preserved the existing behaviour by default but now buildtool.pl has a > "-t toolchainname" argument and buildpacket.pl has a "--toolchain > toolchainname" argument. Both default to the (new) "toolchain" setting > in conf/buildtool.conf > > Since the name of the toolchain directory has changed (was i386, now > i486-unknown-linux-uclibc) any 'next' developers will need to re-build > their toolchain after they pull my latest changes.
Good work! I've took the chance to rebuild with latest linux kernel 3.2.12 and (once again) without uClibc-pthread_initialize.patch. A first test on my router looks pretty well. buildall.sh shows only package with a pb - yate. Anyway I committed new linux kernel and refreshed uclibc buildtool setup to git. kp ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
