From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] fakeroot does not apply patches
Date: Fri, 15 Dec 2006 14:45:37 +0100 [thread overview]
Message-ID: <20061215134537.GA13485@aon.at> (raw)
In-Reply-To: <200612151417.58106.uli@suse.de>
On Fri, Dec 15, 2006 at 02:17:57PM +0100, Ulrich Hecht wrote:
>Hi!
>
>This patch makes sure the no-docs patch for fakeroot is applied when
>building for the target.
Several packages unpack their sources twice. These should ideally be
build out of tree for one make (i'd generally do it for the dir2, i.e.
the host).
Uli, could you perhaps try if fakeroot builds out of tree? Several
packages may not support this and should receive upstream-fixes to make
them behave, IMHO.
TIA,
Bernhard
next prev parent reply other threads:[~2006-12-15 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 13:17 [Buildroot] [patch] fakeroot does not apply patches Ulrich Hecht
2006-12-15 13:45 ` Bernhard Fischer [this message]
2006-12-15 14:07 ` Ulrich Hecht
2006-12-15 14:21 ` Bernhard Fischer
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=20061215134537.GA13485@aon.at \
--to=rep.nop@aon.at \
--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