From: Thomas Marteau <marteaut@esiee.fr>
To: "Markus Döhr" <doehrm@aubi.de>
Cc: "'parisc-linux@lists.parisc-linux.org'"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Newbie on PA: Trying to compile kernel
Date: Tue, 09 Oct 2001 23:55:20 +0200 [thread overview]
Message-ID: <3BC37248.8D97FE2C@esiee.fr> (raw)
In-Reply-To: 7B1EED0C5D58D411B73200508BDE77B2C53CA9@EXCHANGEB
Hi again,
>
> No, I'd like to do a native linux-kernel-on-linux compile.
Damn it, I did well but it was the stuff for you. I am sure it will help
some one else :-)
> I'm compiling kernels since 1.9.X (don't remember exactly) on INTEL and
> Sparc, but never did on parisc. So I did the following:
I hope you have time. Compiling with 712 is fun but long :(
> The documents tell me to use either NFS or a RAMDISK in palo/Makefile and
> _here's_ the problem (or the documents are outdated). I'll try the manual
> approach and see what'll happen.
These documents were written at a time when HDD were not so well
supported.
If you just want to update your kernel, you just do
apt-get update
apt-get upgrade # in order to get the last gcc version
after that, you follow what I said about make menuconfig...
I tested this way of producing kernel a long time ago. I am sure it will
be ok.
FYI, the ramdisk or NFSroot is needed if you do a make palo but you do
only make vmlinux!
> PS-OT: I wonder if SAP will port their application server to parisc/Linux...
I really do not know. Perhaps, Helge Deller will know :)
Good Luck anyway, Thomas.
ESIEE Team
next prev parent reply other threads:[~2001-10-09 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 21:51 [parisc-linux] Newbie on PA: Trying to compile kernel Markus Döhr
2001-10-09 21:55 ` Thomas Marteau [this message]
2001-10-09 23:33 ` Randall Craig
2001-10-10 9:11 ` Helge Deller
-- strict thread matches above, loose matches on Subject: below --
2001-10-09 20:15 Markus Döhr
2001-10-09 21:16 ` Thomas Marteau
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=3BC37248.8D97FE2C@esiee.fr \
--to=marteaut@esiee.fr \
--cc=doehrm@aubi.de \
--cc=parisc-linux@lists.parisc-linux.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.