From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc3-mm3 woes
Date: Mon, 11 Oct 2004 23:00:46 +0900 [thread overview]
Message-ID: <416A920E.6050709@tequila.co.jp> (raw)
In-Reply-To: <1097465881.1418.4.camel@krustophenia.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/11/2004 12:38 PM, Lee Revell wrote:
> On Sun, 2004-10-10 at 23:23, Clemens Schwaighofer wrote:
>
>>System: debian/unstable
>>
>>I just tried 2.6.9-rc3-mm3 and I have two problems:
>>
>>- - he calls himself 2.6.9-rc-mm31, yeah 31. I don't know where this comes
>>from, because in the Makefile itself it is mm3. Whatever makes him do
>>that, I don't know, but he install himselfs like this, perhaps the
>>problems come from that
>>
>
>
> Weird. Works fine here. Maybe this is a bug in the debian build
> process, try building from a fresh tree.
I'll build from kernel.org vanilla 2.8.1 + rc3 + mm3 patch.
>>- - cdrecord segfaults. Again I don't know if this is cdrecords fault or
>>not, but cdrecord works fine with 2.6.9-rc2-mm1
>>
> You might need to back out this patch:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc3/2.6.9-rc3-mm3/broken-out/optimize-profile-path-slightly.patch
oh thanks. I'll try that.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBapIOjBz/yQjBxz8RAjqyAJ9trl/eSGibfYIi6m0JggVK56IZCgCfWztG
yhT4j2QQy4c+p3Uk5c7ntD0=
=NBMG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-10-11 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 3:23 2.6.9-rc3-mm3 woes Clemens Schwaighofer
2004-10-11 3:38 ` Lee Revell
2004-10-11 14:00 ` Clemens Schwaighofer [this message]
2004-10-11 5:47 ` Mike Houston
2004-10-11 14:01 ` Clemens Schwaighofer
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=416A920E.6050709@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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.