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:50:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205166@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205165@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Type: message/rfc822, Size: 1577 bytes --]
From: "Jeff V. Merkey" <jmerkey@timpanogas.com>
To: linux-kernel@vger.rutgers.edu
Subject: IA64 version of 2.4.0-test1 has compile errors/config errors
Date: Mon, 19 Jun 2000 12:43:28 -0600
Message-ID: <394E69D0.E867BCBF@timpanogas.com>
The IA64 build of 2.4.0-test1 reports type mismatch errors for strlen()
and memset() with the latest build of linux-2.4.0-test1 at
www.kernel.org when you build the kernel under the NUE environment with
the GCC IA64 compiler/linker. The compile error indicates a conflict
with built in functions with the same name.
The .config file is also has sone issues. When you follow the
instructions that come with SKI and NUE for IA64, they instruct you to
copy the kernel.config file that comes with the IA64 SKI simulator file
system over the default .config in the /linux main build directory.
After running "make config" or "make oldconfig", several config options
get deleted from .config such as CONFIG_SIMETH=y, CONFIG_SIM_SERIAL=y,
and CONFIG_SIM_SCSI=y and have to be "hacked in" manually or the target
vmlinux file does not get built properly and will not load correctly
with SKI.
Also, IA32 emulation support is listed in .config as "experimental", but
seems to work ok when enabled. The lack of loadable module support also
seems troublesome. I am assuming modutils have not been modified to
support IA64?
:-)
Jeff
prev parent reply other threads:[~2000-06-19 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 20:49 [Linux-ia64] [Fwd: IA64 version of 2.4.0-test1 has compile errors/config errors] Jeff V. Merkey
2000-06-19 20:50 ` Jeff V. Merkey [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-105590678205166@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