From: Andrew Morton <akpm@osdl.org>
To: larry.finger@att.net (Larry.Finger@lwfinger.net)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Broken "make install" in 2.6.14-git1
Date: Sun, 30 Oct 2005 11:26:32 -0800 [thread overview]
Message-ID: <20051030112632.10fd92de.akpm@osdl.org> (raw)
In-Reply-To: <103020050105.8134.43641C43000AEB8F00001FC621603831169D0A09020700D2979D9D0E04@att.net>
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?
next prev parent reply other threads:[~2005-10-30 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 1:05 Larry.Finger@lwfinger.net
2005-10-30 19:26 ` Andrew Morton [this message]
2005-10-30 22:03 Larry.Finger@lwfinger.net
2005-10-30 22:19 ` Andrew Morton
2005-10-31 2:52 ` Larry W. Finger
2005-10-30 22:53 Larry.Finger@lwfinger.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051030112632.10fd92de.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=larry.finger@att.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®