From: Adam Carter <adamcarter3@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Adding an extra patch to an ebuild
Date: Thu, 22 Nov 2012 09:06:31 +1100 [thread overview]
Message-ID: <CAC=wYCF9xpCx7zRnct0sKrNyFD0G-419bQsE0yUKz7_Sc+ShtA@mail.gmail.com> (raw)
In-Reply-To: <20121121104136.1032871b@digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
>
> Create /etc/portage/env/sys-devel/gcc-4.7.2 containing
>
> post_src_unpack() {
> cd "${S}"
> epatch_user
> }
>
> to run epatch_user after the source has been unpacked. If you need to run
> epatch_user after the other patches have been applied, change the function
> name to post_src_prepare.
>
Thanks Neil, this worked beautifully, as did the gcc patch and i'm running
4.7.2.
[-- Attachment #2: Type: text/html, Size: 652 bytes --]
prev parent reply other threads:[~2012-11-21 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 8:38 [gentoo-user] Adding an extra patch to an ebuild Adam Carter
2012-11-21 9:41 ` Markos Chandras
2012-11-21 9:46 ` Adam Carter
2012-11-21 9:46 ` Helmut Jarausch
2012-11-21 10:17 ` Markos Chandras
2012-11-21 10:41 ` Neil Bothwick
2012-11-21 22:06 ` Adam Carter [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='CAC=wYCF9xpCx7zRnct0sKrNyFD0G-419bQsE0yUKz7_Sc+ShtA@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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