From: Samuel Flory <sflory@rackable.com>
To: "Chandler, Neville" <chandler@ibiquity.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: non-SMP kernels fail to compile
Date: Thu, 18 Dec 2003 15:20:31 -0800 [thread overview]
Message-ID: <3FE2363F.70708@rackable.com> (raw)
In-Reply-To: <E3C9701D2F6B57468EBB36C053176EEF0172198F@mail.ibiquity.com>
Chandler, Neville wrote:
> Hello,
>
> I'm having problems compiling Non-SMP versions of the linux kernel.
> linux-2.4.23 and linux-2.4.24-pre1 fail to compile with SMP disabled.
> However, they do compile cleanly when SMP is enabled. Any help would be
> appreciated.
>
> Thanks.
>
> System: Redhat 9
> GCC: 3.3.2
>
>
I've compiled a number of up kernel for 2.4.23 with no issue. What
sort of compile errors are you getting? Can we get you config file.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-12-18 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 18:24 non-SMP kernels fail to compile Chandler, Neville
2003-12-18 23:20 ` Samuel Flory [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 9:25 Kevin Curtis
2003-12-19 14:17 Chandler, Neville
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=3FE2363F.70708@rackable.com \
--to=sflory@rackable.com \
--cc=chandler@ibiquity.com \
--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