public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [Fwd: IA64 version of 2.4.0-test1 has compile errors/config errors]
Date: Mon, 19 Jun 2000 20:49:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205165@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]

 

[-- Attachment #2: Type: message/rfc822, Size: 2904 bytes --]

From: "Jeff V. Merkey" <jmerkey@timpanogas.com>
To: Jes Sorensen <jes@linuxcare.com>
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: IA64 version of 2.4.0-test1 has compile errors/config errors
Date: Mon, 19 Jun 2000 14:39:26 -0600
Message-ID: <394E84FE.520F31A6@timpanogas.com>


"Separate but equal" was ruled by the US Supreme Court to be an invalid
concept relative to civil rights cases -- I think it's probably a good
precedent for Linux.  I understand that the IA64 folks should get the
message in the most efficient manner possible, but unless I am mistaken,
there's only "one" master Linux tree, and unless the two are planned to
diverge, www.kernel.org should be the central repository for IA64, just
like any other Linux port, otherwise, we get the current situation --
the build at www.kernel.org is not always current or at the expected
level of completeness that the rest of Linux enjoys.  It took me over
four hours Sunday to locate and download all the patches and fixes from
www.ia64linux.org and hp.com to get the build from www.kernel.org to
even compile for IA64.  It was a "jolting" experience, and I could see
where your average Linux user who was trying to get IA64 Linux up and
running could be left with the impression that it's "not quite cooked".

At any rate, I'll forward it on, but this list should be the correct
forum for Linux general issues, and at some point, IA64 should merge
competely with this linux effort, since it's the primary source for most
people on Planet Earth who run Linux.

:-)

Very Truly Yours,

Jeff


Jes Sorensen wrote:
> 
> >>>>> "Jeff" == Jeff V Merkey <jmerkey@timpanogas.com> writes:
> 
> Jeff> The IA64 build of 2.4.0-test1 reports type mismatch errors for
> Jeff> strlen() and memset() with the latest build of linux-2.4.0-test1
> Jeff> at www.kernel.org when you build the kernel under the NUE
> Jeff> environment with the GCC IA64 compiler/linker.  The compile
> Jeff> error indicates a conflict with built in functions with the same
> Jeff> name.
> 
> It would be a good idea if you used the linux-ia64@linuxia64.org
> mailing list for this kinda stuff as instructed on the Web page where
> you downloaded SKI and NUE. There is a much bigger chance that the
> appropriate people will read it there.
> 
> Jeff> Also, IA32 emulation support is listed in .config as
> Jeff> "experimental", but seems to work ok when enabled.  The lack of
> Jeff> loadable module support also seems troublesome.  I am assuming
> Jeff> modutils have not been modified to support IA64?
> 
> There is currently no module support, though it should be coming
> shortly.
> 
> Jes

             reply	other threads:[~2000-06-19 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-19 20:49 Jeff V. Merkey [this message]
2000-06-19 20:50 ` [Linux-ia64] [Fwd: IA64 version of 2.4.0-test1 has compile errors/config errors] Jeff V. Merkey

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-105590678205165@msgid-missing \
    --to=jmerkey@timpanogas.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