From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: Compiling the kernel in ultralinux
Date: Wed, 13 Jan 1999 09:01:26 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91621942727750@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91621280925272@msgid-missing>
>
> Hello,
>
> I have just installed 1.1.19 (Jan11) in a ultra1. I downloaded the kernel
> source and after config I followed the usual steps: make dep; make clean,
> but when I do "make zImage" I just got:
>
> # make zImage
> make: *** No rule to make target `zImage'. Stop.
>
> I have compiled exactly the same kernel (2.2.0-pre6) in a i386
> without any problem.
>
> I know this sounds stupid, but... did I miss to install any package? Any
> hint?
The usual steps on archs other than i386 are different:
make config; make dep; make clean; make; make modules; make modules_install
and you're done.
And, currently kernel.org kernel won't compile and/or run, as quite some
things are not merged yet from vger to Linus.
The only way how to get a kernel is anoncvs, but that's currently shut down.
But, if you install the kernel-source rpms, you should have a quite recent
2.2.0-pre6 kernel.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux | http://ultra.linux.cz/ | http://ultra.penguin.cz/
Linux version 2.2.0-pre6 on a sparc64 machine (3958.37 BogoMips)
___________________________________________________________________
prev parent reply other threads:[~1999-01-13 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-13 7:23 Compiling the kernel in ultralinux Alejandro Aguilar Sierra
1999-01-13 9:01 ` Jakub Jelinek [this message]
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=marc-linux-ultrasparc-91621942727750@msgid-missing \
--to=jj@sunsite.ms.mff.cuni.cz \
--cc=ultralinux@vger.kernel.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.