mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Robert Palmer <robert.palmer@ingenutec.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] How to patch a rule file
Date: Fri, 24 Feb 2012 17:20:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120224T180224-862@post.gmane.org> (raw)

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

Neither case seems to even attempt to execute the patch

Any assistance on this would be greatly appreciated


-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2012-02-24 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 17:20 Robert Palmer [this message]
2012-02-29 22:05 ` Jerry Kirk
2012-03-01  6:52 ` Bernhard Walle

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=loom.20120224T180224-862@post.gmane.org \
    --to=robert.palmer@ingenutec.com \
    --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