Messages in this thread | | | Date | Sun, 30 Oct 2005 11:26:32 -0800 | From | Andrew Morton <> | Subject | Re: Broken "make install" in 2.6.14-git1 |
| |
larry.finger@att.net (Larry.Finger@lwfinger.net) wrote: > > The changes introduced the commit 596c96ba05e5d56e72451e02f93f4e15e17458df break the initrd building step of the "make install" process. The console output is as follows:
I'm unable to locate that commit, perhaps due to a local lack of gittiness.
Can you describe the patch less cryptically?
> >sudo make install > CHK include/linux/version.h > CHK include/linux/compile.h > SKIPPED include/linux/compile.h > CHK usr/initramfs_list > Kernel: arch/i386/boot/bzImage is ready (#97) > sh /home/finger/kernel/linux/arch/i386/boot/install.sh 2.6.14-g596c96ba arch/i386/boot/bzImage System.map "/boot" > Root device: /dev/hda6 (mounted on / as reiserfs) > Module list: via82cxxx processor thermal fan reiserfs > > Kernel image: /boot/vmlinuz-2.6.14-g596c96ba > Initrd image: /boot/initrd-2.6.14-g596c96ba > Shared libs: lib/ld-2.3.5.so lib/libblkid.so.1.0 lib/libc-2.3.5.so lib/libselinux.so.1 lib/libuuid.so.1.2 > Driver modules: via82cxxx processor thermal fan reiserfs > Filesystem modules: > Including: klibc initramfs udev fsck.reiserfs > Bootsplash: SuSE (1024x768) > 8358 blocks > no record for '/block/hdc/uevent' in database > Use of uninitialized value in scalar chomp at > /usr/lib/perl5/vendor_perl/5.8.7/Bootloader/Tools.pm line 139. > Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.7/Bootloader/Tools.pm line 140. > ...... > > I used git bisect to localize the bad commit. I also observed that if the kernel created /sys/block/hdc/uevent, it failed. If this "file" does not exist, the install worked.
What does "it failed" mean? Is this the same bug, or a different one? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |