From: Uros Prestor <uros@turbolinux.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Kernel panic in dtlb_fault
Date: Fri, 12 Jan 2001 19:36:48 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005039@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205904@msgid-missing>
"Mallick, Asit K" wrote:
> Attached is a patch to fix the problem. Uros and Jenna were able to boot
> with this patch. Sorry for sending the early version.
Something is still not kosher if you enable CONFIG_DISABLE_VHPT=y. If I try
recompiling the gnupro RPM the compilation breaks down immediately after the
config stage With the following error:
# rpm -ba /usr/src/turbo/SPECS/gnupro.spec
...
creating ./config.status
creating Makefile
Configuring utils...
Created "Makefile" in /work/BUILD/gnupro-2.96/build/utils
Configuring spu...
Created "Makefile" in /work/BUILD/gnupro-2.96/build/utils/spu
++ perl -e 'if( -x "/usr/bin/getconf" && ( ($p=`/usr/bin/getconf
_NPROCESSORS_ONLN`) >= 0 ) ){ print "$p"} else { print "1"; }'
+ make -j 2
/bin/sh: SHELL: command not found
/bin/sh: -c: command not found
make: *** [all-libiberty] Error 127
make: *** Waiting for unfinished jobs....
Bad exit status from /var/tmp/rpm-tmp.82077 (%build)
Things become very bizarre if you try to compile by hand, ranging from
reports of missing /lib/libc.so.6.1 to internal compiler errors... This
happens both on 2xB3 BigSur and 4xB3 Lion. If I revert to the kernel which
enables VHPT the compilation goes just fine.
Uros
--
Uros Prestor
uros@turbolinux.com
next prev parent reply other threads:[~2001-01-12 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 23:03 [Linux-ia64] Kernel panic in dtlb_fault Uros Prestor
2001-01-10 0:40 ` Uros Prestor
2001-01-10 3:15 ` Mallick, Asit K
2001-01-11 1:14 ` Mallick, Asit K
2001-01-11 19:09 ` Uros Prestor
2001-01-11 19:35 ` David Mosberger
2001-01-11 20:12 ` Uros Prestor
2001-01-11 20:23 ` Mallick, Asit K
2001-01-11 22:10 ` Mallick, Asit K
2001-01-12 19:36 ` Uros Prestor [this message]
2001-01-15 23:08 ` Mallick, Asit K
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-105590693005039@msgid-missing \
--to=uros@turbolinux.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.