From: rml@ufl.edu
To: <linux-kernel@vger.kernel.org>
Subject: [WEIRD] working kernel off RH7's gcc-2.96!?
Date: Tue, 21 Nov 2000 00:19:12 -0500 [thread overview]
Message-ID: <974783952.3a1a05d0c4840@webmail.ufl.edu> (raw)
i dont want to revisit the flame fest (at all, please) but it seems i have been
using a kernel that successfully compiled under RedHat 7's gcc snapshot (2.96).
i normally use gcc-2.91.66 for everything (mv kgcc gcc) but just synced my
system with rawhide, so the gcc/kgcc pair is back on my system and i forgot. so
i recompiled to test11 yesterday, and:
[00:05:51]rml@phantasy:~# cat /proc/version
Linux version 2.4.0-test11 (rml@phantasy) (gcc version 2.96 20000731 (Red Hat
Linux 7.0)) #1 Mon Nov 20 19:06:06 EST 2000
the odd thing is, not only did it compile, but my machine has been up for a day
with heavy use in X with a full-featured kernel! not only no OOPSs, but no bugs!
the only thing i thought of was that alan's kgcc detection routine was in-place,
and using the detected kgcc to compile but then doing a hardcoded use of "gcc"
to grab the version ... but i could not find the code by grepping.
so i went ahead and removed kgcc from my path and recompiled, and sure enough --
it compiled fine.
just fyi, but someone tell me i am on crack... regardless, i am about to reboot
into a gcc-2.91.66 kernel.
--
Robert M. Love
rml@tech9.net
rml@ufl.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-21 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 5:19 rml [this message]
2000-11-21 14:57 ` [WEIRD] working kernel off RH7's gcc-2.96!? Jes Sorensen
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=974783952.3a1a05d0c4840@webmail.ufl.edu \
--to=rml@ufl.edu \
--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