From: "Mohammad A. Haque" <mhaque@haque.net>
To: Jes Sorensen <jes@linuxcare.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Russell King <rmk@arm.linux.org.uk>,
Philip Blundell <philb@gnu.org>,
junio@siamese.dhis.twinsun.com, Manuel McLure <manuel@mclure.org>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.3-ac12
Date: Sun, 22 Apr 2001 12:30:00 -0400 [thread overview]
Message-ID: <3AE30708.6DF72C1D@haque.net> (raw)
In-Reply-To: <E14rJw2-0005r5-00@the-village.bc.nu> <d366fw29sv.fsf@lxplus015.cern.ch>
In case everyone missed my original patch =P
http://marc.theaimsgroup.com/?l=linux-kernel&m=98791931115515&w=2
Jes Sorensen wrote:
>
> >>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> Alan> The recommended compilers for non x86 are different too - eg you
> Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
> Alan> on.
>
> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.
>
> Maybe it's time to move that check to the arch include dir instead?
>
> Jes
> -
> 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/
--
=====================================================================
Mohammad A. Haque http://www.haque.net/
mhaque@haque.net
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
batmanppc@themes.org
=====================================================================
next prev parent reply other threads:[~2001-04-22 16:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 2:53 Linux 2.4.3-ac12 Alan Cox
2001-04-22 4:17 ` Manuel McLure
2001-04-22 5:47 ` junio
2001-04-22 6:07 ` junio
2001-04-22 10:42 ` Philip Blundell
2001-04-22 12:26 ` Alan Cox
2001-04-22 12:43 ` Philip Blundell
2001-04-22 12:54 ` Alan Cox
2001-04-22 13:00 ` Philip Blundell
2001-04-22 13:10 ` Alan Cox
2001-04-22 13:22 ` Russell King
2001-04-22 13:29 ` Alan Cox
2001-04-22 16:12 ` Jes Sorensen
2001-04-22 16:30 ` Mohammad A. Haque [this message]
2001-04-22 17:27 ` Roman Zippel
2001-04-22 17:43 ` Jes Sorensen
2001-04-22 18:42 ` Alan Cox
2001-04-23 6:54 ` Geert Uytterhoeven
2001-04-22 13:51 ` Philip Blundell
2001-04-22 12:11 ` Alan Cox
2001-04-22 12:18 ` Russell King
2001-04-22 12:51 ` Alan Cox
2001-04-22 12:55 ` John Jasen
2001-04-22 13:00 ` Alan Cox
2001-04-22 8:57 ` Eyal Lebedinsky
2001-04-22 12:20 ` Alan Cox
2001-04-22 13:04 ` Eyal Lebedinsky
2001-04-22 16:25 ` John Cavan
2001-04-22 17:07 ` Manuel McLure
2001-04-22 18:48 ` Alan Cox
2001-04-22 18:57 ` Manuel McLure
2001-04-22 18:59 ` Linux 2.4.3-ac12 unresolved symbol rwsem J Sloan
2001-04-23 0:19 ` Linux 2.4.3-ac12 John Cavan
2001-04-23 8:35 ` Byeong-ryeol Kim
2001-04-23 22:18 ` Byeong-ryeol Kim
2001-04-22 22:46 ` Mr. James W. Laferriere
2001-04-22 13:48 f5ibh
2001-04-22 14:03 ` Jesper Juhl
2001-04-22 17:26 Dieter Nützel
2001-04-22 19:53 ` J . A . Magallon
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=3AE30708.6DF72C1D@haque.net \
--to=mhaque@haque.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jes@linuxcare.com \
--cc=junio@siamese.dhis.twinsun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel@mclure.org \
--cc=philb@gnu.org \
--cc=rmk@arm.linux.org.uk \
/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 NNTP newsgroup(s).