From: <exister99@velocitus.net>
To: <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: 64 bit kernel in the name of HIGHMEM
Date: Mon, 13 Oct 2003 17:15:19 -0600 (MDT) [thread overview]
Message-ID: <38866.156.153.254.10.1066086919.squirrel@webmail.rmci.net> (raw)
In-Reply-To: <20031009140319.GA17647@linux-mips.org>
Hi Ralf,
Thanks for the prompt response.
> Reminds me of the HP Laserjet code in the kernel. Anybody still using
> or testing that?
Yes, the code I am working with is basically a snapshot of the kernel
source with /arch/mips/hp-lj etc.
> Anyway, for a 64-bit processor such as the 20Kc I suggest a 64-bit
> kernel. Highmem is a pain and 64-bit is the cure.
To that end I have been trying to build a 64 bit kernel. I think I am
going about it correctly. Got ahold of
mips64el-linux-binutils-2.14-3.i386.rpm
mips64el-linux-boot-gcc-2.95.4-9.i386.rpm
and got cranking. Currently make is dying with the following output:
[root@l51dhcp252 ljlinux]# make ARCH=mips64 CROSS_COMPILE=mips64el-linux-
. scripts/mkversion > .tmpversion
mips64el-linux-gcc -D__KERNEL__ -I/home/astone/cf_burn_64/ljlinux/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -I/usr/lib/gcc-lib/mips64el-linux/2.95.4/include
-fomit-frame-pointer -Dx_unity_x -I
/home/astone/cf_burn_64/ljlinux/include/asm/gcc -mabi=64 -G 0
-mno-abicalls -fno-pic -Wa,--trap -pipe -DUTS_MACHINE='"mips64"'
-DKBUILD_BASENAME=version -c -o init/version.o init/version.c
mips64el-linux-gcc -D__KERNEL__ -I/home/astone/cf_burn_64/ljlinux/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -I/usr/lib/gcc-lib/mips64el-linux/2.95.4/include
-fomit-frame-pointer -Dx_unity_x -I
/home/astone/cf_burn_64/ljlinux/include/asm/gcc -mabi=64 -G 0
-mno-abicalls -fno-pic -Wa,--trap -pipe -DKBUILD_BASENAME=do_mounts -c
-o init/do_mounts.o init/do_mounts.c
cpp0: output pipe has been closed
mips64el-linux-gcc: Internal compiler error: program cc1 got fatal signal 11
make: *** [init/do_mounts.o] Error 1
Initial searches claim this is a bug in the compiler. Could it be due to
something I am doing wrong? Any guidance on building a 64 bit kernel
would be greatly appreciated.
Best Regards, Andrew Stone
WARNING: multiple messages have this Message-ID (diff)
From: <exister99@velocitus.net>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: 64 bit kernel in the name of HIGHMEM
Date: Mon, 13 Oct 2003 17:15:19 -0600 (MDT) [thread overview]
Message-ID: <38866.156.153.254.10.1066086919.squirrel@webmail.rmci.net> (raw)
Message-ID: <20031013231519.xa-ORZ6Cgi6XrOgXgT5muJfbH_nZH0S1hc-jUtXv_2g@z> (raw)
In-Reply-To: <20031009140319.GA17647@linux-mips.org>
Hi Ralf,
Thanks for the prompt response.
> Reminds me of the HP Laserjet code in the kernel. Anybody still using
> or testing that?
Yes, the code I am working with is basically a snapshot of the kernel
source with /arch/mips/hp-lj etc.
> Anyway, for a 64-bit processor such as the 20Kc I suggest a 64-bit
> kernel. Highmem is a pain and 64-bit is the cure.
To that end I have been trying to build a 64 bit kernel. I think I am
going about it correctly. Got ahold of
mips64el-linux-binutils-2.14-3.i386.rpm
mips64el-linux-boot-gcc-2.95.4-9.i386.rpm
and got cranking. Currently make is dying with the following output:
[root@l51dhcp252 ljlinux]# make ARCH=mips64 CROSS_COMPILE=mips64el-linux-
. scripts/mkversion > .tmpversion
mips64el-linux-gcc -D__KERNEL__ -I/home/astone/cf_burn_64/ljlinux/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -I/usr/lib/gcc-lib/mips64el-linux/2.95.4/include
-fomit-frame-pointer -Dx_unity_x -I
/home/astone/cf_burn_64/ljlinux/include/asm/gcc -mabi=64 -G 0
-mno-abicalls -fno-pic -Wa,--trap -pipe -DUTS_MACHINE='"mips64"'
-DKBUILD_BASENAME=version -c -o init/version.o init/version.c
mips64el-linux-gcc -D__KERNEL__ -I/home/astone/cf_burn_64/ljlinux/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -I/usr/lib/gcc-lib/mips64el-linux/2.95.4/include
-fomit-frame-pointer -Dx_unity_x -I
/home/astone/cf_burn_64/ljlinux/include/asm/gcc -mabi=64 -G 0
-mno-abicalls -fno-pic -Wa,--trap -pipe -DKBUILD_BASENAME=do_mounts -c
-o init/do_mounts.o init/do_mounts.c
cpp0: output pipe has been closed
mips64el-linux-gcc: Internal compiler error: program cc1 got fatal signal 11
make: *** [init/do_mounts.o] Error 1
Initial searches claim this is a bug in the compiler. Could it be due to
something I am doing wrong? Any guidance on building a 64 bit kernel
would be greatly appreciated.
Best Regards, Andrew Stone
next prev parent reply other threads:[~2003-10-13 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 22:00 mips 32 bit HIGHMEM support exister99
2003-10-08 22:00 ` exister99
2003-10-09 14:03 ` Ralf Baechle
2003-10-09 22:11 ` bug in kernel_entry? Steve Scott
2003-10-09 22:11 ` Steve Scott
2003-10-10 13:23 ` Ralf Baechle
2003-10-10 14:59 ` mips 32 bit HIGHMEM support Ralf Baechle
2003-10-13 23:15 ` exister99 [this message]
2003-10-13 23:15 ` 64 bit kernel in the name of HIGHMEM exister99
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=38866.156.153.254.10.1066086919.squirrel@webmail.rmci.net \
--to=exister99@velocitus.net \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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.