public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Newbie: General Complile Issues
Date: Mon, 17 Nov 2003 15:48:15 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106908480024444@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106908237920741@msgid-missing>

On Mon, 2003-11-17 at 08:19, Dan Am wrote:
> Hi,
> sorry to to bother the gurus with mere admin view questions. I got hold of a 
> zx6000 with RHAS 2.1, got the book and I am taking her out for a spin, so to 
> speak.  
> Here goes: 
> 
> 1. Which is the "correct" source ? Kernel Org or bkbits ? 

   Either, for 2.4 make sure you have Bjorn's patch or use his bk tree
(linux-ia64-2.4).  For 2.6, you don't need the ia64 patch, but, see next
answer.

> 2. Will the 2.6-test1 that I am using (compiling now with gcc3.1 from hpl) not 
> run ? 

   test9 definitely works, via kernel.org, standard bk or ia64 bk. 
Unless you really need test1, I'd go with the latest.  I don't remember
how well test1 worked.

> 3. There is talk of "Mosberger Patches" : Are those required ?  Where can they
>     be found ? 
> 

   For 2.4, yes, but they're now Bjorn patches.   They are not required
for 2.6.  You can find them all here:
http://www.kernel.org/pub/linux/kernel/ports/ia64/

> Thanks a million for bothering. Of course, if there is a FAQ on those q's, or 
> a better list, I'd be reading that. Grateful for a pointer in that case. 
> 

   You might want to check http://www.gelato.org, there's some useful
information there.  Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


      reply	other threads:[~2003-11-17 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 15:19 Newbie: General Complile Issues Dan Am
2003-11-17 15:48 ` Alex Williamson [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=marc-linux-ia64-106908480024444@msgid-missing \
    --to=alex.williamson@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox