From: Keith Owens <kaos@ocs.com.au>
To: Alexander.Riesen@synopsys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 2.1 is available
Date: Tue, 23 Apr 2002 09:03:34 +1000 [thread overview]
Message-ID: <5928.1019516614@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 22 Apr 2002 16:36:06 +0200." <20020422163606.A1142@riesen-pc.gr05.synopsys.com>
On Mon, 22 Apr 2002 16:36:06 +0200,
Alex Riesen <Alexander.Riesen@synopsys.com> wrote:
>On Sun, Apr 21, 2002 at 05:43:08PM +1000, Keith Owens wrote:
>>
>> Release 2.1 of kernel build for kernel 2.5 (kbuild 2.5) is available.
>> http://sourceforge.net/projects/kbuild/, Package kbuild-2.5, download
>> release 2.1.
>>
>
>Hi, i've got some problems with 2.1:
>.../v2.5-1/arch/i386/kernel/entry.S:223: unterminated character constant
>.../v2.5-1/arch/i386/kernel/entry.S:264: unterminated character constant
>.../v2.5-1/arch/i386/kernel/entry.S:280: unterminated character constant
>That was Linus's bk tree (cset 1.562)
>+ kbuild-2.5-core-4
>+ kbuild-2.5-common-2.5.8-pre3-1
>+ kbuild-2.5-i386-2.5.8-pre3-1
Those are not release 2.1 files, you are using old patches. Release
2.1 uses core-6 and patches for 2.5.8, not 2.5.8-pre3.
>P.S. "phase 1" for xconfig is evil, is it absolutely unavoidable?
Yes. A driver may not be in the main kernel source tree, it can be in
a separate tree. Phase 1 finds all the files in all trees, including
config files.
next prev parent reply other threads:[~2002-04-22 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 7:43 Announce: Kernel Build for 2.5, Release 2.1 is available Keith Owens
2002-04-21 13:53 ` Keith Owens
2002-04-21 14:32 ` Daniel Phillips
2002-04-22 23:00 ` Keith Owens
2002-04-21 23:04 ` Daniel Phillips
2002-04-22 23:54 ` Keith Owens
2002-04-22 23:57 ` Keith Owens
2002-04-22 14:36 ` Alex Riesen
2002-04-22 23:03 ` Keith Owens [this message]
2002-04-23 9:23 ` Alex Riesen
2002-04-23 22:29 ` 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=5928.1019516614@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=Alexander.Riesen@synopsys.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