From: Gene Heskett <gene.heskett@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: 2.6.36, make oldconfig broken
Date: Fri, 22 Oct 2010 20:54:51 -0400 [thread overview]
Message-ID: <201010222054.52066.gene.heskett@gmail.com> (raw)
In-Reply-To: <4CC20011.5010809@oracle.com>
[-- Attachment #1: Type: Text/Plain, Size: 1999 bytes --]
On Friday, October 22, 2010, Randy Dunlap wrote:
>On 10/22/10 13:08, Gene Heskett wrote:
>> On Friday, October 22, 2010, Randy Dunlap wrote:
>>> On Fri, 22 Oct 2010 12:29:36 -0400 Gene Heskett wrote:
>>>
>>> [adding linux-kbuild]
>>>
>>>> Greets all;
>>>>
>>>> I have managed to get 2.6.36 to a semi-usable state, but I have major
>>>> breakage yet.
>>>>
>>>> Question: what happens if I simply move my working 2.6.35.7 .config
>>>> into the 2.6.36 tree and build it from that?
>>>
>>> I think that it runs 'make oldconfig' automatically for you.
>>>
>>>> It can't be any worse than what the broken 'make oldconfig' did to
>>>> it. What it output changed the disk drivers, graphic card drivers
>>>> and just plain threw away at least a hundred lines in the multimedia
>>>> drivers section.
>
>When I use your config-2.6.36.7 file on 2.6.36 and run 'make oldconfig',
Correction, that config was from 2.6.35.7.
>I don't see anything like changes in disk or graphics card drivers and
>I don't see 100 or more lines thrown away in the multimedia drivers.
>
>Did you use 'make oldconfig' or did you use that script that you have
>mentioned and posted in the past? Could it be causing problems?
My script (buildit26) takes an old argument and a new argument, that and
any patch names needed are edited into it, not passed as arguments,
although I have thought of doing that, but as that can lead to typu's
getting past these old fingers, I don't trust me doing it with live
arguments. It copy's the old .configs to /tmp long enough to unpack the
new, then copy's them into the new tree. And they do a make oldconfig after
any patches have been applied.
It hasn't been edited since I ran it, so I'll attach it. Maybe you can see
something I missed.
Thanks Randy.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
About the only thing on a farm that has an easy time is the dog.
[-- Attachment #2: buildit26 --]
[-- Type: application/x-shellscript, Size: 2928 bytes --]
next prev parent reply other threads:[~2010-10-23 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 16:29 Re:2.6.36, make oldconfig broken Gene Heskett
2010-10-22 18:40 ` 2.6.36, " Randy Dunlap
2010-10-22 20:08 ` Gene Heskett
2010-10-22 21:20 ` Randy Dunlap
2010-10-23 0:54 ` Gene Heskett [this message]
2010-10-23 1:39 ` Ken Moffat
2010-10-23 2:43 ` Gene Heskett
2010-10-24 1:36 ` Randy Dunlap
2010-10-24 5:13 ` Gene Heskett
2010-10-25 14:23 ` Gene Heskett
2010-10-23 1:07 ` Ken Moffat
2010-10-23 2:18 ` Gene Heskett
2010-10-23 13:41 ` Ingo Molnar
2010-10-23 16:26 ` Gene Heskett
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=201010222054.52066.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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.