mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Solar Designer <solar@openwall.com>
To: musl@lists.openwall.com
Subject: Re: cluts makefiles
Date: Wed, 10 Aug 2011 07:06:34 +0400	[thread overview]
Message-ID: <20110810030634.GC28119@openwall.com> (raw)
In-Reply-To: <4E419688.5030005@gmail.com>

Luka -

On Tue, Aug 09, 2011 at 10:20:24PM +0200, Luka Mar??eti?? wrote:
> On 08/09/2011 06:11 PM, Vasiliy Kulikov wrote:
> >>Hunk #1 FAILED at 7.
> >>1 out of 1 hunk FAILED -- saving rejects to file a/Makefile.rej
> >You should use "-p1".  With -p0 patch doesn't remove any prefix
> >directories and tries to change files b/defines.mk and similar.
> 
> Where should this be run? I tried root where a/ and b/ are, and also in 
> the b/ itself. In both cases, the same thing happens. Maybe it is me who 
> messed up line 7 now, I don't know. :-/

To apply a patch, you do not need two trees, and you do not need to
match the top-level directory names to those seen in the patch file.
Rather, you may do something like:

cp -a cluts cluts-to-patch
cd cluts-to-patch
patch -p1 < ../patch-file

or just:

cd cluts
patch -p1 < ../patch-file

but the first approach may be preferable if you haven't yet made the
determination to fully apply the patch to your tree (so you want to
experiment on a copy first).

Here are some instructions/examples on how to generate patches and how
to apply them:

http://openwall.info/wiki/how-to-make-patches
http://openwall.info/wiki/john/how-to-extract-tarballs-and-apply-patches

You may want to experiment with this for your own changes to cluts -
just so that you know how it works - before you apply a patch provided
to you by someone else.

Alexander


  reply	other threads:[~2011-08-10  3:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 11:30 Vasiliy Kulikov
2011-08-09 15:48 ` Luka Marčetić
2011-08-09 16:11   ` Vasiliy Kulikov
2011-08-09 20:20     ` Luka Marčetić
2011-08-10  3:06       ` Solar Designer [this message]
2011-08-10 11:29         ` Luka Marčetić
2011-08-10 11:49           ` Solar Designer

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=20110810030634.GC28119@openwall.com \
    --to=solar@openwall.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).