From: "Anthony Barbachan" <barbacha@Hinako.AMBusiness.com>
To: "Peter Samuelson" <peter@cadcamlab.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Unable to compile the 2.2.18 kernel
Date: Mon, 11 Dec 2000 02:50:02 -0500 [thread overview]
Message-ID: <000b01c06346$f8680100$0ac809c0@hotmail.com> (raw)
In-Reply-To: <001f01c06323$db434d00$0ac809c0@hotmail.com> <20001211001723.Z6567@cadcamlab.org>
Thanks. I missed that this time when I modified the Makefile. I didn't pay
close attention to the new script code in there to check for the kernel
compiler.
----- Original Message -----
From: "Peter Samuelson" <peter@cadcamlab.org>
To: "Anthony Barbachan" <barbacha@hinako.ambusiness.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>; "Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>
Sent: Monday, December 11, 2000 1:17 AM
Subject: Re: Unable to compile the 2.2.18 kernel
>
> [Anthony Barbachan]
> > I am unable to compile the latest kernel. I have attached my kernel
> > configuration and a copy of the output of where the compile fails. I
> > am looking into what is causing the compile failure, but have not
> > been able to figure it out yet. Still looking though.
>
> It looks like you overrode the 'CC' make variable, either by editing
> the toplevel Makefile or at the command line. This works fine in 2.4,
> but in 2.2 you need to pass extra flags to the compiler:
>
> make zImage
CC="/usr/local/gcc-2.7.2.3/bin/gcc -I$(pwd)/include -D__KERNEL__"
>
> ...for example.
>
> Peter
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-11 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 3:38 Unable to compile the 2.2.18 kernel Anthony Barbachan
2000-12-11 6:17 ` Peter Samuelson
2000-12-11 7:50 ` Anthony Barbachan [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='000b01c06346$f8680100$0ac809c0@hotmail.com' \
--to=barbacha@hinako.ambusiness.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.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