i was curious about what it would take to build only the appropriate toolchain for the moment from a fresh checkout of openwrt (and whether that's even a reasonable question to ask).
for example, let's say i want to build a toolchain for my ASUS WL-500gP with broadcom wifi. what this suggests is that i have to run "make menuconfig", but i shouldn't need to specify a great deal of information -- only that which is necessary to do the toolchain build, right? so, from what i see, i absolutely need to specify: * the target system (BCM947xx, 2.6 kernel) * the target profile (BCM43xx wifi) beyond that, i might mess around under the "Toolchain Options" menu and change, oh: * binutils version * gcc version or anything else in that submenu but, for now, i'll just leave those selections where they are. theoretically, would that be sufficient, at which point i can run $ make toolchain/install note that i haven't made any selections regarding packages but i shouldn't have to -- i'm not doing *anything* regarding building a final image so i should be able to ignore all of the rest of "make menuconfig" for now, is that correct? (in fact, do i even need to select the target profile correctly for this?) i also wasn't sure whether i even needed to build the host tools first so i skipped that, and ran "make V=99 toolchain/install", and got: ... --: /home/rpjday/openwrt/wl-500gp/build/trunk/staging_dir/host/bin/sed: No such file or directory ... $ ah, as i've mentioned in a posting some time back, openwrt insists on building and using its own "sed" even if one is already available, so i just hacked the tools build to build only "sed" as an experiment, then "make tools/install" to get that locally-built "sed", and once again took a shot at: $ make toolchain/install and, at the moment, the build is humming along nicely. which inspires the following questions: * should i expect to be able to build a toolchain from a fresh checkout? given that there is a "toolchain/install" target, one concludes that this should be legal. * should i need to "make tools/install" first? AFAICT, the only reason you need to do that is to get "sed", and if the build process was smart enough to use the local "sed" if it was available, that step wouldn't be necessary. * finally, what is the list of menuconfig options that might affect the toolchain build, and once i build that toolchain, can i come back later and finish the configuration without having to re-do any of that earlier work? in short, once i have a toolchain, can i just pick up where i left off to finish configuring and building my loadable image? thanks muchly. 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
