On Sun, 3 Feb 2008, [EMAIL PROTECTED] wrote: > > given more platforms, isn't it theoretically possible to configure > > for another platform that just happens to use mipsel and be based > > on gcc-4.1.2 as well? and if that were the case, wouldn't that > > second build step all over the previous build? > > > > in short, unless you can guarantee complete separation between > > different target platforms when you're configuring and building, > > i'm not sure there's much value in trying to make a "clean" try to > > be that selective. > > > > or am i missing something? > > You're right.
oh, good, i didn't want to seem even more clueless than usual. :-) > Pls see attached patch. The BUILD_SUFFIX is used to separate > different platforms. Currently the toolchain dir is not unique > enough. You can't have the same gcc and different uclibc versions > for the same arch. > > The applied patch does not fix the ./tmp dir . Unless the ./tmp is > not unique it's not possible to run different builds in parallel > (for instance in an compute farm). > > At least sequential build are is possible with this patch. You can > easily change between different platforms without loosing the > previous builds. i'll take a look at it, as i remember having to invent something exactly like this for an embedded project i was working on once upon a time. my admittedly misinformed opinions shortly. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA Home page: http://crashcourse.ca Fedora Cookbook: http://crashcourse.ca/wiki/index.php/Fedora_Cookbook ======================================================================== _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
