From: Adam Schrotenboer <adam@tabris.net>
To: gcc@gcc.gnu.org
Subject: Linux Kernel, KDE & GCC 3.0.3
Date: Thu, 13 Dec 2001 23:33:00 -0000 [thread overview]
Message-ID: <20011214071034.7FB20FB80F@tabris.net> (raw)
Have the KDE issues been resolved in 3.0.3? also, what of the Kernel 2.4
8139too.c ICE?
I'm kind of hoping that we don't have to wait for GCC 3.1 to fix these issues.
One more parting shot. Does GLIBC compile w/ GCC 3.0.3? (I don't exactly
expect it to, but it would be _really_ nice)
--
tabris
Official Project Stages:
1. Uncritical Acceptance
2. Wild Enthusiasm
3. Dejected Disillusionment
4. Total Confusion
5. Search for the Guilty
6. Punishment of the Innocent
7. Promotion of the Non-participants
next reply other threads:[~2001-12-14 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 23:33 Adam Schrotenboer [this message]
2001-12-14 7:57 ` Craig Rodrigues
2001-12-14 9:12 ` Franz Sirl
2001-12-14 18:31 ` GNATS Login was " Adam Schrotenboer
2001-12-14 22:56 ` Craig Rodrigues
2001-12-15 4:30 ` Gerald Pfeifer
2001-12-15 2:00 ` Andreas Jaeger
2001-12-16 23:09 ` GNATS Login Jason Molenda
2001-12-16 23:16 ` Craig Rodrigues
2001-12-16 23:28 ` Jason Molenda
2001-12-17 8:35 ` Craig Rodrigues
2001-12-21 1:08 ` Gerald Pfeifer
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=20011214071034.7FB20FB80F@tabris.net \
--to=adam@tabris.net \
--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).