> I am new to building uclibc, but have experience building glibc and newlib, > and I > have a question about the best way to build multiple versions of uclibc from a > script without any user interaction. > > Currently, I run 'make defconfig' to create a default .config file and then > use grep > to modify the .config file before each build (strip out some lines and then > append > my versions back in). I.e. I remove the ARCH_BIG_ENDIAN=y line and then add > in a ARCH_LITTLE_ENDIAN=y line. to change from big-endian to little-endian or > I > may pick a different MIPS ABI. But what I noticed is that when I run the > normal > 'make' command after modifying .config is that my .config changes are getting > wiped out and .config is getting restored to a default state. > > Can someone explain why this is happening and if there is a way to prevent > it? Is > there a better way to do multiple uclibc builds with different defaults and > without > requiring any user interaction?
Modifying the .config manually is generally bad. The best way to do it I'd say is by running menuconfig for each config you want then copy the generated .config to a different file. In your script then simply copy the saved config file to replace the .config before running make. You might want to run make oldconfig after replacing .config to ensure any new values your config files doesn't have would be resolved to default. HTH, Qais _______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc
