On Thu, Oct 29, 2009 at 6:36 PM, Ralf Mardorf <[email protected]>wrote:
> rosea grammostola wrote: > > There is. But I'm wondering if it's different when I just build for my > > own system or for 'all' pc's. > > How do I know which packages I should have installed for the kernel > > build, to support as much hardware as possible... > > For the kernel build it's not important what packages you have got > installed. Important is, that you keep the CPU type at x86 or x86_64 > instead of optimizing it e.g. to amd64. This is in the config: # # CONFIG_64BIT is not set CONFIG_X86_32=y # CONFIG_X86_64 is not set CONFIG_X86=y CONFIG_OUTPUT_FORMAT="elf32-i386" > It's also important that you > don't fit the number of CPUs to your hardware, keep it at e.g. 512 > instead of using 2. Where can I find that? This is in the config: # # Digest # CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m > This issues, timer resolution, rt support etc. is > set by the config file. Copy /boot/config-2.6.29-1-multimedia-amd64 to > your source directory and rename it to .config, then load it when you > run "# make menuconfig", if needed, IIRC I didn'd need to copy the > config file. For the build you might need: > fakeroot > gcc > kernel-package > make > libncurses5-dev > Btw. the patch command has got a --dry-run option. --dry-run option?
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
