All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Huizenga <gerrit@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?
Date: Mon, 13 Nov 2000 22:25:36 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205703@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205680@msgid-missing>

I've built Jim's 1024 toolchain release this way.

I have not yet played with the test10 kernel - I'm still on test9 because
of the number of patches I'm using, not all of which are yet at test10
(actually, the last one or two was just announced, so I can probably move
up a notch soon).

You might want to look into just why it won't boot.  There are several
workarounds (e.g. qlc > 4GB memory addressing turned on in BIOS, EFI
workarounds, kernel config parameters such as VHPT and related workarounds
enabled/disabled, etc.).  Your problem may not be just the toolchain.

gerrit

> >I was able to build this toolchain (the lack of pre-existing g++ stuff
> >on my IA64 machine was a small problem but I ignored it for the time
> >being).  I installed it into a /usr/gcc1024 hierarchy so as not to
> >clobber my existing gcc (since I'm not yet moving to glibc 2.2 on
> >that machine).
> 
> Which toolchain are you building?
> 
> >Then I could build the kernel (on a Red Hat Linux release 6.93 (Zoot))
> >release, cut sometime in June, I believe.
> >
> >Then, I built the kernel with:
> >
> >HOSTCC=/usr/bin/gcc CC=/usr/gcc1024/bin/gcc make HOSTCC=/usr/bin/gcc
> >CC=/usr/gcc1024/bin/gcc -j 20 > ERRS 2>&1 &
> >
> >Which seems to work reasonably well.  This allows the cross tools to
> >build with the native CC (glibc 2.1 based) and the kernel to build
> >with a recent compiler, which does not care a whit about glibc
> >support.
> >
> >The native toolchain on that Red Hat distro does not have unwind
> >support, impylying no stack tracebacks in panics, kdb, etc.  The newer
> >gcc works fine, compiles completely, and has wonderful stack
> >tracebacks.
> >
> >All this on a 4-proc Lion, running A3 procs and an ancient BIOS/frame
> >(my B2/B3 upgrade has been deferred for a while).
> 
> I'm trying to build the 2.4.0-test10 kernel with the ia64 patch.  We
> recently upgaded the hardware on one of our boxes to B1 stepping, and
> now it won't boot.  I'm hoping the newer kernel will work better.
> 
> So far, I'm running into problems with the old Red Hat toolchain, and
> with the latest snapshot as well.  I haven't hit on the right compiler
> yet, I guess.
> 
> Has anyone successfully built 2.4.0-test10 with the IA64 patch?  If so,
> which toolchain did you use?
> 
> - Scott
> 
> -----------------------------
> Scott Hankin                  In the beginning, there was nothing, then
> Rational Software             God said, "Let there be light."  And there
> 20 Maguire Road               was light.  There was still nothing, but
> Lexington, MA 02421           you could see it a lot better.
> 


  parent reply	other threads:[~2000-11-13 22:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 11:14 [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Francis Galiegue
2000-11-10 14:17 ` Jes Sorensen
2000-11-10 14:49 ` [Linux-ia64] Recommended compiler for compiling kernels test10 Francis Galiegue
2000-11-10 22:47 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-12 20:41 ` [Linux-ia64] Recommended compiler for compiling kernels test1 Pimenov, Sergei
2000-11-13 20:23 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 20:34 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper? Jim Wilson
2000-11-13 20:38 ` [Linux-ia64] Recommended compiler for compiling kernels test1 Broadfoot, KenX
2000-11-13 20:52 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper? H . J . Lu
2000-11-13 20:59 ` H . J . Lu
2000-11-13 21:14 ` Jim Wilson
2000-11-13 21:17 ` H . J . Lu
2000-11-13 21:19 ` [Linux-ia64] Recommended compiler for compiling kernels test10 " Jim Wilson
2000-11-13 21:23 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 " Jim Wilson
2000-11-13 21:38 ` [Linux-ia64] Recommended compiler for compiling kernels test10 " Gerrit Huizenga
2000-11-13 22:00 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 22:09 ` Scott Hankin
2000-11-13 22:10 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 and Jun Nakajima
2000-11-13 22:25 ` Gerrit Huizenga [this message]
2000-11-13 22:36 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 22:37 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-13 22:44 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 23:01 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-13 23:06 ` Gerrit Huizenga
2000-11-13 23:08 ` H . J . Lu
2000-11-13 23:14 ` Jim Wilson
2000-11-13 23:31 ` Don Dugger
2000-11-13 23:33 ` Jim Wilson
2000-11-14  0:24 ` Don Dugger
2000-11-15 17:59 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-15 19:52 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-16  2:51 ` H . J . Lu

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=marc-linux-ia64-105590678205703@msgid-missing \
    --to=gerrit@us.ibm.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.