public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wayne.Brown@altec.com
To: "J . A . Magallon" <jamagallon@able.es>,
	Cort Dougan <cort@fsmlabs.com>,
	gmack@innerfire.net, Jeff Garzik <jgarzik@mandrakesoft.com>,
	Andrew Morton <andrewm@uow.edu.au>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Gregory Maxwell <greg@linuxpower.cx>,
	Mark Hahn <hahn@coffee.psychology.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where did kgcc go in 2.4.0-test10 ?
Date: Thu, 2 Nov 2000 14:53:33 -0600	[thread overview]
Message-ID: <8625698B.0072B9BF.00@smtpnotes.altec.com> (raw)



A number of people have pointed out to me that egcs-1.1.2 is weak on C++
support.  Rather than clutter up the list by replying to all of them, I've
picked this one to say "Thank you" to everyone who responded.  I'm not a C++
programmer, so I tend to forget about it and think of gcc as just a C compiler.
Now this discussion makes more sense to me.

I agree that if there is going to be a separate compiler for the kernel, the
Makefiles should be flexible enough to allow the user to plug in whatever
compiler he or she prefers to use.

Wayne




"J . A . Magallon" <jamagallon@able.es> on 11/02/2000 06:40:58 AM

To:   Wayne Brown/Corporate/Altec@Altec
cc:   linux-kernel@vger.kernel.org

Subject:  Re: Where did kgcc go in 2.4.0-test10 ?




On Thu, 02 Nov 2000 06:46:04 Wayne.Brown@altec.com wrote:
>
>
> I've been following this kgcc discussion with interest for weeks now and
> there's
> one thing that still puzzles me.  Everyone on both sides of the issue seems to
> be saying that kgcc (AKA egcs 1.1.2) is used because the gcc versions shipped
                       ^^^^^^^^^^^^^^^
Wrong assumption. The idea is if I need a way to set a compiler for kernel
that is not the same compiler as the system wide one. Should kernel Makefiles
use gcc (hardcoded) (and people must have a 'gcc' that works for kernel), or
let kernel use something called 'kgcc', and let user decide if in his machine
kgcc is 2.7, egcs or 2.95.2.

> by
> several vendors don't compile the kernel correctly.  What I haven't seen yet
> is
> an explanation of why kgcc can't be used for compiling *everything* and why
> another compiler even needs to be installed.

Because gcc is not only the C compiler, is the full compiler system.
The support for C++ in 2.95 has nothing to do with egcs. And 2.95 supports
java, for example.
And the libraries. The C++ standard library is much better in 2.95 that in
egcs.


--
Juan Antonio Magallon Lacarta                          mailto:jamagallon@able.es

-
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/





-
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/

             reply	other threads:[~2000-11-02 20:54 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 20:53 Wayne.Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-02  5:46 Where did kgcc go in 2.4.0-test10 ? Wayne.Brown
2000-11-02  6:48 ` Jeff Garzik
2000-11-02 11:46 ` Alan Cox
2000-11-02 12:40 ` J . A . Magallon
2000-11-01 22:40 J . A . Magallon
2000-11-01 22:53 ` Alan Cox
2000-11-02  1:12   ` Jeff Garzik
2000-11-02  2:47     ` J . A . Magallon
2000-11-02  3:26       ` Jeff Garzik
2000-11-02 11:40         ` Alan Cox
2000-11-01 22:57 ` Kurt Garloff
2000-11-01 22:47   ` David S. Miller
2000-11-01 22:45     ` Gérard Roudier
2000-11-01 23:07     ` Ben Pfaff
2000-11-01 23:12       ` David S. Miller
2000-11-01 23:11     ` Alan Cox
2000-11-01 23:15       ` Jeff Garzik
2000-11-01 23:21     ` Tom Rini
2000-11-01 23:30       ` Alan Cox
2000-11-01 23:36         ` Tom Rini
2000-11-02  0:22         ` Jeff Garzik
2000-11-02  4:50           ` Mike Galbraith
2000-11-02  4:59             ` Jeff Garzik
2000-11-01 23:37     ` Nathan Paul Simons
2000-11-01 23:29       ` David S. Miller
2000-11-01 23:54         ` Cort Dougan
2000-11-01 23:45           ` David S. Miller
2000-11-02  0:00             ` Cort Dougan
2000-11-02  0:54               ` Alan Cox
2000-11-02  0:21             ` Nathan Paul Simons
2000-11-02  0:11               ` David S. Miller
2000-11-02  0:32                 ` H. Peter Anvin
2000-11-02  0:59                   ` Bill Nottingham
2000-11-02  2:42             ` Marc Lehmann
2000-11-02 21:24             ` Gérard Roudier
2000-11-02 22:37               ` David S. Miller
2000-11-02  6:28           ` Jakub Jelinek
2000-11-02  0:11         ` Nathan Paul Simons
2000-11-02  0:06           ` David S. Miller
2000-11-02  0:22           ` Tom Rini
2000-11-02  0:26           ` Jeff Garzik
2000-11-02  0:56           ` Alan Cox
2000-11-02  0:17     ` Miquel van Smoorenburg
2000-11-02  0:30       ` Jeff Garzik
2000-11-02  1:01         ` Miquel van Smoorenburg
2000-11-01 23:04   ` George
2000-11-02  1:08     ` Jan Dvorak
2000-11-01 23:12   ` Alan Cox

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=8625698B.0072B9BF.00@smtpnotes.altec.com \
    --to=wayne.brown@altec.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrewm@uow.edu.au \
    --cc=cort@fsmlabs.com \
    --cc=gmack@innerfire.net \
    --cc=greg@linuxpower.cx \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --cc=jamagallon@able.es \
    --cc=jgarzik@mandrakesoft.com \
    --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