mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to patch a rule file
Date: Thu, 01 Mar 2012 07:52:44 +0100	[thread overview]
Message-ID: <4F4F1CBC.9060607@bwalle.de> (raw)
In-Reply-To: <loom.20120224T180224-862@post.gmane.org>

Am 24.02.12 18:20, schrieb Robert Palmer:
> I've searched the archives (unfortunately "patch" is VERY common) 
> and I read the "How to become a PTXdist Guru" from the pengutronix 
> web site.  In section 4.1.2 patch series, it gives an overview of 
> patching and it then list the search order, giving FOUR cases.  
> The last case is "bug fixing" and it goes on to describe that this 
> case is intended for patching rules in the PTXdist rule files.  
> This is EXACTLY what I need to do, unfortunately, that's the last 
> thing is says about this case.
> 
> specifically, I'm using ptxdist-2010.08.0 and GNU Make v3.82.
> I'm trying to build the OSELAS toolchain, so I'm working with 
> that as the "project" directory
> 
> in the ptxdist rules there is apache2.make which needs to be
> patched to run under Make v3.82 (there is a missing line 
> continuation character)
> 
> I have tried building a patch in my toolchain (project) /patches folder 
> 
> a) naming the patch folder (package) 'apache2'  
>        -- matching the rule name found in ptxdist/rules
> b) naming the folder 'httpd-2.0.58'
>        -- matching the package name as described in the rule makefile

You can't patch the rules file. Just copy it to your project, it
overwrites the default one.


Regards,
Bernhard

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2012-03-01  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 17:20 Robert Palmer
2012-02-29 22:05 ` Jerry Kirk
2012-03-01  6:52 ` Bernhard Walle [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=4F4F1CBC.9060607@bwalle.de \
    --to=bernhard@bwalle.de \
    --cc=ptxdist@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