From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: Joshua ChaitinPollak <jpollak@kivasystems.com>
Subject: Re: [gentoo-embedded] portage patching fails with busybox's patch
Date: Tue, 27 Jun 2006 20:22:29 -0400 [thread overview]
Message-ID: <200606272022.29471.vapier@gentoo.org> (raw)
In-Reply-To: <BD4FE4EC-8DF2-4E09-BD69-3696A96319BC@kivasystems.com>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
On Tuesday 27 June 2006 18:28, Joshua ChaitinPollak wrote:
> when emerging, portage passes the patch command the -g option, but
> busybox doesn't support this and fails. Is there a way to prevent
> portage from using -g
edit EPATCH_OPTS in /usr/portage/eclass/eutils.eclass
> or is this a bug I should file?
certainly not, unless you file the bug with busybox to add support for -g
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
prev parent reply other threads:[~2006-06-28 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 22:28 [gentoo-embedded] portage patching fails with busybox's patch Joshua ChaitinPollak
2006-06-28 0:22 ` Mike Frysinger [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=200606272022.29471.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=jpollak@kivasystems.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox