Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Simen Thoresen <simen-tt@online.no>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] compiling (and booting) on a 735
Date: Tue, 28 Sep 1999 21:30:46 +0200	[thread overview]
Message-ID: <199909281924.VAA02857@online.no> (raw)

I've now downloaded the ramdisk.bin image (0903), and have compiled with
that. The compile worked, and I'm now sitting with a probably nonworking
kernel :-)

How do I boot?

I'v killed the filesystem on my 2nd disk, doing cat vmlinux >
/dev/dsk/c0t2d0 . No great loss, as I'v emtied it of useful data, and was
planning to do that anyway. Unfortunately, when I boot from P1, IPL
responds with 'bad LIF magic'. back to hpux, then....

Do I need a tftp-server and try for a netboot?


make menuconfig:
I've downloaded ncurses (v 4.2 from ftp.gnu.org,
/gnu/ncurses/ncurses-4.2.tar.gz ) and installed it.

I then linked /usr/local/include (where ncurses.h resides) to
/usr/include/ncurses
(so that /usr/include/ncurses/ncurses.h exists), and sssslightly modified
linux/scripts/lxdialog/Makefile, as HPUX's find barfed on 
-maxdepth 1.

sh-2.03$ diff Makefile.old Makefile
33c33
<       @x=`find /lib/ /usr/lib/ /usr/local/lib/ -maxdepth 1 -name
'libncurses.*
'` ;\
---
>       @x=`find /lib/ /usr/lib/ /usr/local/lib/ -name 'libncurses.*'` ;\

Running make menuconfig from the kernel directory now works great, and I
can build nonworking kernels with gusto.

-Simen Thoresen - finally hacking something useful.
--
"We do have a summer. Last year, I remember, it was a Wednesday" 
-Helga-Marie Johnesen, Norwegian citizen, TIME international.

GNUsig v0.9A R3
Support the GNUsig-project! Mail simen-tt@online.no for details.

             reply	other threads:[~1999-09-28 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-28 19:30 Simen Thoresen [this message]
1999-09-28 19:28 ` [parisc-linux] compiling (and booting) on a 735 Philipp Rumpf

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=199909281924.VAA02857@online.no \
    --to=simen-tt@online.no \
    --cc=parisc-linux@thepuffingroup.com \
    /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