From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patch files with Makefile.autotools.in
Date: Wed, 20 Aug 2008 10:03:27 +0200 [thread overview]
Message-ID: <20080820080327.GB19268@mx.loc> (raw)
In-Reply-To: <20080820090529.649c4477@atmel.com>
On Wed, Aug 20, 2008 at 09:05:29AM +0200, Hans-Christian Egtvedt wrote:
>On Tue, 19 Aug 2008 19:45:21 -0400
>"hartleys" <hartleys@visionengravers.com> wrote:
>
>> Monday, August 18, 2008 10:56 PM, Hans-Christian Egtvedt wrote:
>
><snipp problems with patching a custom package>
>
>> I see the "Patching $($(PKG)_DIR_PREFIX)/$($PKG)_NAME)" message but
>> when I examine the source the patch is not present.
>>
>> I think the problem is related to the FIXME note above the rule. I'm
>> trying to apply a patch to a package that is not supplied in
>> buildroot. To keep it separate I have the package in
>> package/customize/<package
>> name>.
>>
>
>Yes, you are indeed a victim of the FIXME, since you do not use the
>"standard" package/<package name> directory structure.
>
>> Any ideas on how to fix the FIXME?
>>
>
>A quick fix would be to just symlink package/customize/<package name>
>to package/<package name>.
>
>I'll do a mental note of the problem, it is likely to show up in the
>future as well.
heh, that was exactly the reason why i added that nice FIXME in the
first place ;)
What secret package is this about anyway? If it's of general use, it
should be added to the tree..
next prev parent reply other threads:[~2008-08-20 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 16:42 [Buildroot] Patch files with Makefile.autotools.in hartleys
2008-08-19 5:56 ` Hans-Christian Egtvedt
2008-08-19 23:45 ` hartleys
2008-08-20 7:05 ` Hans-Christian Egtvedt
2008-08-20 8:03 ` Bernhard Reutner-Fischer [this message]
2008-08-20 8:22 ` Hans-Christian Egtvedt
2008-08-20 16:09 ` hartleys
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=20080820080327.GB19268@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