An alternative approach that worked for me: I've set up an Athlon-based machine (not a laptop) using the Up2date utility. I installed the standard RH CDs and then when up2date ran it automatically detected the new kernel requirements and downloaded them. The machine is running fine. Therefore, I did not need to build the RPMs.
Hope that helps.
Peter
On Wed, 2003-01-01 at 13:43, Bret Hughes wrote:
I need to build a kernel for my duron based laptop that I recently upgraded to 7.3 from 7.2 and broke win4lin in the process. Netraverse suggests that you make sure you can sucessfully build a kernel before adding the win4lin patches and so I DLed the latest kernel source from updates.redhat.com, 2.4.18-19.7.x and installed it. I then copied the athlon config file from the configs dir and ran make menuconfig to make sure I was seeing the correct .config file and sure enough, the athlon stuff was selected. I added test to the release name in the specfile and ran rpmbuild -ba kernel-2.4.spec The build completed and I ended up with an rpms in RPMS/i386 with the names like kernel-2.4.18-19.7.xtest.i386.rpm I was expecting to get rpms in the athlon dir and named athlon. What did I end up with? do I need to run rpmbuild with --target athlon-linux-gnu in order to get athlon rpms? I am about to do that now but since it takes a while on this duron 800 I thought I would ask the gurus. I found references in the archives that suggested that adding optflags: athlon -O3 -march=athlon-xp to /usr/lib/rpm/rpmrc is good. Do I need to do this as well? What is it that the cpu type settings in the .config file do if not ensure that the kernel is optimized for the specified architecture? TIA Bret
|
