Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "marc " <marc@centraltx.com>
To: marc <marc@centraltx.com>, "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
Cc: <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Building my first kernel
Date: Wed,  5 Jun 2002 22:34:19 -0500	[thread overview]
Message-ID: <200206052234.AA1633878578@mail.centraltx.com> (raw)

Call me crazy, but I cannot get this to work. There doesn't seem
to be a 'palo' target for make. When I run make palo it just
runs the make all (below are the first few lines).

Any Ideas?

seki:/usr/src/kernel-source-2.4.18-hppa# make palo
. scripts/mkversion > .tmpversion
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.18-hppa/include -Wall -Wstrict-pro
totypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
 -D__linux__ -pipe -fno-strength-reduce -mno-space-regs -mfast-indirect-calls -m
disable-fpregs -ffunction-sections -march=1.1 -mschedule=7100  -DUTS_MACHINE='"p
arisc"' -c -o init/version.o init/version.c
make CFLAGS="-D__KERNEL__ -I/usr/src/kernel-source-2.4.18-hppa/include -Wall -Ws
trict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -f
no-common -D__linux__ -pipe -fno-strength-reduce -mno-space-regs -mfast-indirect
-calls -mdisable-fpregs -ffunction-sections -march=1.1 -mschedule=7100 " -C  ker
nel
make[1]: Entering directory `/usr/src/kernel-source-2.4.18-hppa/kernel'
make all_targets
make[2]: Entering directory `/usr/src/kernel-source-2.4.18-hppa/kernel'
make[2]: Nothing to be done for `all_targets'.
make[2]: Leaving directory `/usr/src/kernel-source-2.4.18-hppa/kernel'
make[1]: Leaving directory `/usr/src/kernel-source-2.4.18-hppa/kernel'
make CFLAGS="-D__KERNEL__ -I/usr/src/kernel-source-2.4.18-hppa/include -Wall -Ws
trict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -f
no-common -D__linux__ -pipe -fno-strength-reduce -mno-space-regs -mfast-indirect
-calls -mdisable-fpregs -ffunction-sections -march=1.1 -mschedule=7100 " -C  dri
vers

---------- Original Message ----------------------------------
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
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.
>
>

             reply	other threads:[~2002-06-06  3:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06  3:34 marc  [this message]
2002-06-06  3:46 ` [parisc-linux] Building my first kernel Carlos O'Donell Jr.
  -- strict thread matches above, loose matches on Subject: below --
2002-06-06 14:58 marc 
2002-06-06  9:06 Kenneth Westelinck
2002-06-06  4:39 marc 
2002-06-06  7:19 ` Helge Deller
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=200206052234.AA1633878578@mail.centraltx.com \
    --to=marc@centraltx.com \
    --cc=carlos@baldric.uwo.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox