From: "Eric M. Hopper" <hopper@omnifarious.mn.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm 0.9 kernel build problems
Date: Thu, 30 Nov 2000 05:42:21 -0600 [thread overview]
Message-ID: <20001130054221.A26692@omnifarious.mn.org> (raw)
In-Reply-To: <20001130024449.J1381@wookimus.net>; from chewie@wookimus.net on Thu, Nov 30, 2000 at 02:44:49AM -0600
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Thu, Nov 30, 2000 at 02:44:49AM -0600, Chewie wrote:
> On Wed, Nov 29, 2000 at 10:47:09PM +0100, Falcon wrote:
> > You must to change gcc by kgcc in the Makefile
>
> <rant>
> Is it just me, or does this sound like a Red Hat-like solution? Gee.
> Let's package an old version of gcc just so we can compile the kernel
> correctly. We can't simply use a stable gcc as our standard compiler.
> We have to reach back into the bag of the ancients to keep our
> machines running and make it LOOK like we're using the bleeding edge
> with gcc 2.96!
> </rant>
If I'm not mistaken, the reasons the new gcc won't compile the
kernel have more to do with the kernel than with the new gcc. This
problem has happened several times in the past, and it was usually (with
one notable exception in gcc 2.7.1) the kernel's fault.
Have fun (if at all possible),
--
The best we can hope for concerning the people at large is that they
be properly armed. -- Alexander Hamilton
-- Eric Hopper (hopper@omnifarious.mn.org http://www.omnifarious.org/~hopper) --
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-11-30 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 15:05 [linux-lvm] lvm 0.9 kernel build problems Patrick Swartz
2000-11-29 15:41 ` Jay Weber
2000-11-29 17:19 ` Patrick Swartz
2000-11-29 17:22 ` Jay Weber
2000-11-29 22:07 ` Heinz J. Mauelshagen
2000-11-29 21:19 ` Heinz J. Mauelshagen
2000-11-29 21:47 ` Falcon
2000-11-30 8:44 ` Chewie
2000-11-30 10:41 ` Stephen C. Tweedie
2000-11-30 11:42 ` Eric M. Hopper [this message]
2000-11-30 18:46 ` Rik van Riel
2000-11-30 21:01 ` OT: " Chewie
2000-11-30 3:48 ` Steven Lembark
2000-11-29 22:08 ` Heinz J. Mauelshagen
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=20001130054221.A26692@omnifarious.mn.org \
--to=hopper@omnifarious.mn.org \
--cc=linux-lvm@sistina.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.