From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel patch not applied
Date: Tue, 4 Nov 2008 20:54:37 +0100 [thread overview]
Message-ID: <20081104195437.GA26520@mx.loc> (raw)
In-Reply-To: <49109234.9080406@free.fr>
On Tue, Nov 04, 2008 at 07:19:32PM +0100, Julien Boibessot wrote:
>Hi,
>
>It's quite a long time now, since first email, but I was faced to the
>problem today, when updating my old buildroot to the latest svn one.
>
>Bernhard Fischer a ?crit :
>> On Mon, May 14, 2007 at 07:21:25AM +0200, Hans-Christian Egtvedt wrote:
>>
>>> On Fri, 2007-05-11 at 17:40 +0200, Bernhard Fischer wrote:
>>>
>>>> On Fri, May 11, 2007 at 04:31:49PM +0200, Hans-Christian Egtvedt wrote:
>>>>
>>> <cut>
>>>
>>>
>>>>> $(LINUX_HEADERS_UNPACK_DIR)/.patched:
>>>>> $(LINUX_HEADERS_UNPACK_DIR)/.unpacked
>>>>> toolchain/patch-kernel.sh $(LINUX_HEADERS_UNPACK_DIR)
>>>>> toolchain/kernel-headers \
>>>>> linux-$(LINUX_HEADERS_VERSION)-\*.patch.\*
>>>>> ifeq ($(BR2_PACKAGE_OPENSWAN),y)
>>>>> toolchain/patch-kernel.sh $(LINUX_HEADERS_UNPACK_DIR) package/openswan \
>>>>> linux-$(LINUX_HEADERS_VERSION)-\*.patch.\*
>>>>>
>>>> which means that your shell just doesn't expand ba{r,z}
>>>>
>>> Weird, I tried zsh, bash and sh. I am building on Ubuntu 7.04.
>>>
>>
>> IIRC ubuntu defaults to dash as sh, so make sure that
>> a) SHELL points to /bin/bash (ash may work too)
>> or,
>> b) symlink sh to be bash
>>
>> a) is of course the preferred solution, didn't look if there are direct
>> references to /bin/sh instead of $SHELL in the makefiles, though.
>>
>I'm working on KUbuntu 7.10. (yes, I know it's bad :-) ).
>a) doesn't work for me (even if my SHELL env is pointing to /bin/bash)
>
>only b) or "make SHELL=/bin/bash" are working.
yes. Note that there is also CONFIG_SHELL (which should be used in a
consistent manner everywhere) for $(shell ....) invocations.
>
>It's just a 2 cents feedback, so I'm not waiting for an answer ;-)
Thanks for the feedback, I could imagine that it proves helpful
for somebody.
cheers,
prev parent reply other threads:[~2008-11-04 19:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 14:21 [Buildroot] kernel patch not applied David Claffey
2007-05-10 15:34 ` David Claffey
2007-05-11 14:31 ` Hans-Christian Egtvedt
2007-05-11 15:40 ` Bernhard Fischer
2007-05-11 16:29 ` David Claffey
2007-05-12 10:31 ` Bernhard Fischer
2007-05-29 20:52 ` David Claffey
2007-05-14 5:21 ` Hans-Christian Egtvedt
2007-05-14 7:11 ` Bernhard Fischer
2007-05-14 12:41 ` [Buildroot] Matchbox Support Christopher Reder
2007-05-15 8:46 ` Assen Stoyanov
2007-05-15 10:55 ` Peter Korsgaard
2007-05-14 15:25 ` [Buildroot] kernel patch not applied Hans-Christian Egtvedt
2007-05-14 15:34 ` Bernhard Fischer
2007-05-15 7:47 ` Hans-Christian Egtvedt
2007-05-15 8:53 ` Bernhard Fischer
2007-05-15 10:35 ` [Buildroot] Whats happened to Eric? Ulf Samuelsson
2007-05-15 19:04 ` Erik Andersen
2008-11-04 18:19 ` [Buildroot] kernel patch not applied Julien Boibessot
2008-11-04 19:54 ` Bernhard Reutner-Fischer [this message]
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=20081104195437.GA26520@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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