From: Jes Sorensen <jes@sunsite.dk>
To: Jack Steiner <steiner@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd)
Date: 10 Aug 2001 17:31:32 +0200 [thread overview]
Message-ID: <d3n158ue23.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <200108021242.HAA02573@fsgi055.americas.sgi.com>
In-Reply-To: Jack Steiner's message of "Thu, 2 Aug 2001 07:42:45 -0500 (CDT)"
>>>>> "Jack" == Jack Steiner <steiner@sgi.com> writes:
Jack> I know that at some point we need to convert to native builds
Jack> but right now we dont have sufficient bigsur/lion boxes to do
Jack> that.
Jack> We have not seen any problems with the compiler we are using -
Jack> at least we have not attributed a problem to the compiler.
Jack> Should we upgrade to gcc3.0 yet???
Probably not yet. I would stick to gcc-2.96 based on what you can find
in Red Hat's (or one of the other distributions') ia64 SRPMS.
Jes
prev parent reply other threads:[~2001-08-10 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22393.996723520@kao2.melbourne.sgi.com>
2001-08-02 12:42 ` [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd) Jack Steiner
2001-08-02 13:25 ` [RFC] /proc/ksyms change for IA64 Keith Owens
2001-08-10 15:31 ` Jes Sorensen [this message]
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=d3n158ue23.fsf@lxplus015.cern.ch \
--to=jes@sunsite.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox