From: "Kenneth Westelinck" <kennywest1@hotmail.com>
To: carlos@baldric.uwo.ca, marc@centraltx.com
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Building my first kernel
Date: Thu, 06 Jun 2002 09:06:33 +0000 [thread overview]
Message-ID: <F70qSkZ2On3DnRB0MtS00012bca@hotmail.com> (raw)
Hi,
For what it's worth.
I always build my kernel the i386 way:
make menuconfig
make dep clean bzImage
I always use the nightly snapshots available from ftp.parisc-linux.org/cvs/
.
regards,
Kenneth
>From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
>To: marc <marc@centraltx.com>
>CC: parisc-linux@lists.parisc-linux.org
>Subject: Re: [parisc-linux] Building my first kernel
>Date: Wed, 5 Jun 2002 22:26:52 -0400
>
> > I'm trying to build the 2.4.18 kernel, and everything goes great
> > until I get to the `make bzImage` part and it screams about palo.
> > I'm assuming I need the palo source. is this right??
> >
> > -Marc
> >
>
>Yup.
>
>$SRC-TREE--|
> |--- /linux
> |
> |--- /palo
>
>cd linux;
>make oldconfig;
>make menuconfig; (Fiddle)
>make dep;
>make palo;
>
>This puts the required lifimage in $SRC-TREE/palo
>
>c.
>
>
>_______________________________________________
>parisc-linux mailing list
>parisc-linux@lists.parisc-linux.org
>http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
enjoy life, enjoy linux,
Kenneth
_________________________________________________________________
Verzend en ontvang Hotmail via je mobieltje: http://mobile.msn.com
next reply other threads:[~2002-06-06 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 9:06 Kenneth Westelinck [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 14:58 [parisc-linux] Building my first kernel marc
2002-06-06 4:39 marc
2002-06-06 7:19 ` Helge Deller
2002-06-06 3:34 marc
2002-06-06 3:46 ` Carlos O'Donell Jr.
2002-06-06 1:16 marc
2002-06-06 2:26 ` Carlos O'Donell Jr.
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=F70qSkZ2On3DnRB0MtS00012bca@hotmail.com \
--to=kennywest1@hotmail.com \
--cc=carlos@baldric.uwo.ca \
--cc=marc@centraltx.com \
--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.