From: hermann <brummer-@web.de>
To: Robin Gareus <robin@gareus.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Rusty Russell" <rusty@rustcorp.com.au>,
linux-rt-users@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Grant Likely" <grant.likely@secretlab.ca>,
devicetree-discuss@lists.ozlabs.org, lguest@lists.ozlabs.org
Subject: Re: [PATCH] Various fixups from first bug reports
Date: Sat, 23 Jul 2011 17:21:23 +0200 [thread overview]
Message-ID: <1311434484.2223.12.camel@box> (raw)
In-Reply-To: <4E2ADBB6.20604@gareus.org>
Am Samstag, den 23.07.2011, 16:33 +0200 schrieb Robin Gareus:
> On 07/23/2011 04:19 PM, hermann wrote:
> > Am Samstag, den 23.07.2011, 11:57 +0200 schrieb Robin Gareus:
> >> Hello Herman,
> >>
> >> Are you using make-kpkg? You need to change the path to lguest
> >> in /usr/share/kernel-package/ruleset/targets/doc.mk and two or three
> >> other files there as Rusty outlined.
> >>
> >> HTH,
> >> robin
> >
> > Hi Robin
> >
> > Yes, using make-kpkg. I changed line 61 from
> > [..]
> > but it didn't help, the result is still the same.
> > /usr/bin/make ARCH=i386 \
> > -C Documentation/lguest
>
> That's the one in /usr/share/kernel-package/ruleset/targets/image.mk
>
> I don't remember all locations, there were around a dozen, also
> including some $CONFIG_* checks. It was pretty straight forward and -
> alas - I did not keep a diff.
>
> `grep -rli lguest /usr/share/kernel-package/` should get you going.
>
> If you're really stuck I can `apt-get --reinstall` and create a diff.
> Let me know. If it is Debian, be aware that there are also various other
> scripts in need of patching (e.g. /etc/init.d/udev supported_kernel()
> does not match the 3.X series, yet),..
>
>
> > Schluss.
> ende, aus :)
>
> robin
Thanks robin, get it working now. Have changed the locations in
/usr/share/kernel-package/ruleset/targets/common.mk
/usr/share/kernel-package/ruleset/targets/doc.mk
/usr/share/kernel-package/ruleset/targets/image.mk
It would be cool if you could remember witch other scripts need to be
patched to support the 3.X series.
I mean I run already the Kernel 3.0.0-rc7-rt0 i686 here on debian/sid
without hazel, but be interested to set up all in a matching manner.
regards
hermann
next prev parent reply other threads:[~2011-07-23 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.02.1107211932440.2702@ionos>
[not found] ` <1311278277-8222-1-git-send-email-u.kleine-koenig@pengutronix.de>
[not found] ` <1311313414.2940.8.camel@box>
2011-07-22 6:57 ` [PATCH] Various fixups from first bug reports Uwe Kleine-König
2011-07-22 7:40 ` hermann
2011-07-22 11:04 ` Rusty Russell
[not found] ` <87y5zqzick.fsf-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
2011-07-22 19:20 ` Uwe Kleine-König
[not found] ` <20110722192051.GH16561@pengutronix.de>
2011-07-23 3:17 ` hermann
2011-07-23 9:57 ` Robin Gareus
[not found] ` <4E2A9B18.6030000-+VlDMftONaMdnm+yROfE0A@public.gmane.org>
2011-07-23 14:19 ` hermann
2011-07-23 14:33 ` Robin Gareus
2011-07-23 15:21 ` hermann [this message]
2011-07-23 18:53 ` Uwe Kleine-König
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=1311434484.2223.12.camel@box \
--to=brummer-@web.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=lguest@lists.ozlabs.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=robin@gareus.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).