From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Bernd Schmidt <bernds@redhat.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: e2fsck-1.25 problem (fwd)
Date: Tue, 13 Nov 2001 16:04:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20011123115438.04725008@mail.lauterbach.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111231024070.29248-100000@host162.cambridge .redhat.com>
At 11:26 23.11.2001, Bernd Schmidt wrote:
>Found this on linux-kernel and thought it was interesting. It turns out
>his libgcc_s.so was in /usr/local/lib on a different partition.
>
>I believe we had some discussion about the possibility of this kind of
>breakage when we added the shared libgcc?
Yeah, that's normal if you compile system binaries with a gcc3 that isn't
installed like a system compiler. That's the packagers fault, he should
have made sure that libgcc_s ends up in /lib like it does in the packages I
build for PPC or the rh72 packages that Jakub did.
Franz.
>---------- Forwarded message ----------
>Date: Thu, 22 Nov 2001 22:57:25 -0400
>From: Garst R. Reese <reese@isn.net>
>To: linux-kernel <linux-kernel@vger.kernel.org>
>Subject: e2fsck-1.25 problem
>
>Sorry if I'm OT here, but reading the docs on ext3fs I had to upgrade
>from e2fsck-1.19 so I got the latest, 1.25 and installed it before
>booting 2.4.15pre6.
>make check said all was fine. But, when I rebooted some messages sailed
>by about not being able to load shared libraries and libgcc_s.so.1 and
>fsck said something about errors in the fs and REBOOT NOW. Very scary
>always.
>I booted up a recovery disk and ran e2fsck-1.10 on both of the relevant
>devices and with -f and all was well. I rebooted back to 2.4.14 and got
>the same messages flying by. Nothing of the sort in dmesg or the logs.
>Can anybody give me a clue as to what is going on? The system goes ahead
>and reboots and runs fine with either kernel AFAIK.
>gcc-3.0.2
>cc reese@isn.net
>Thanks a bunch, Garst
>-
>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/
next parent reply other threads:[~2001-11-23 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0111231024070.29248-100000@host162.cambridge .redhat.com>
2001-11-13 16:04 ` Franz Sirl [this message]
2001-11-13 15:45 Bernd Schmidt
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=5.1.0.14.2.20011123115438.04725008@mail.lauterbach.com \
--to=franz.sirl-kernel@lauterbach.com \
--cc=bernds@redhat.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).