From: Mike Fedyk <mfedyk@matchmail.com>
To: Ivanovich <ivanovich@menta.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile problem 2.4.14
Date: Sat, 10 Nov 2001 15:22:14 -0800 [thread overview]
Message-ID: <20011110152214.E446@mikef-linux.matchmail.com> (raw)
In-Reply-To: <01111022150000.00265@gryppas> <01111023170400.01130@localhost.localdomain>
In-Reply-To: <01111023170400.01130@localhost.localdomain>
On Sat, Nov 10, 2001 at 11:17:04PM +0100, Ivanovich wrote:
> On Saturday 10 November 2001 21:15, Panagiotis Moustafellos wrote:
>
> > I am really getting a hard time compiling the 2.4.14..
> > My current system has a 2.4.13 (by patching all the way
> > from 2.4.9), so I patched the sources, yes after make clean,
> > make menuconfig, and make dep ; make bzImage, I get this
> > message (during the compilation of vmlinux )
>
> > Could someone give me some instruction on what could be
> > the problem, and hopefully, how to fix it?
> > Thanks in advance
>
> too much patching can't be good...
> you should get the sources of the 2.4.14 and you'll have less headaches
If the patches are applied properly, and no rejects are noticed, then you
should be able to patch as much as you want, and it will be the same as af
downloading directly from kernel.org.
Now, if there was a previous kernel compile, and then several patches
applied, (say from 2.4.0 all the way up to 2.4.14...) then you'll probably
have to run "make mrproper" as mentioned by Keith...
If I've left anything out, please let me knwo...
Mike
next prev parent reply other threads:[~2001-11-10 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 20:15 Compile problem 2.4.14 Panagiotis Moustafellos
2001-11-10 22:17 ` Ivanovich
2001-11-10 23:22 ` Mike Fedyk [this message]
2001-11-11 4:17 ` Compile problem 2.4.14 [SOLVED] Panagiotis Moustafellos
2001-11-10 22:48 ` Compile problem 2.4.14 Keith Owens
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=20011110152214.E446@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=ivanovich@menta.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox