| 1 |
On Wed, Nov 21, 2012 at 9:46 AM, Helmut Jarausch |
| 2 |
<jarausch@××××××××××××××××.de> wrote: |
| 3 |
> On 11/21/2012 09:38:26 AM, Adam Carter wrote: |
| 4 |
>> |
| 5 |
>> It looks like i have hit this gcc 4.7 build bug: |
| 6 |
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53113 |
| 7 |
>> |
| 8 |
>> Theres a patch attached to the bug i'd like to apply. Unfortunately the |
| 9 |
>> gcc |
| 10 |
>> 4.7.2 ebuild doesnt have "epatch_user", so i need to take the other |
| 11 |
>> approach listed in the handbook. It suggests i use a custom environment |
| 12 |
>> but |
| 13 |
>> i dont understand how i would apply a patch by setting an environment |
| 14 |
>> variable. Can anyone explain? |
| 15 |
>> |
| 16 |
> |
| 17 |
> Please have a look at |
| 18 |
> |
| 19 |
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=6 |
| 20 |
> |
| 21 |
> /etc/portage/patches |
| 22 |
> |
| 23 |
> Helmut. |
| 24 |
> |
| 25 |
|
| 26 |
This requires the ebuild to use epatch_user. |
| 27 |
|
| 28 |
Adam, I don't it is possible to use the 'evn' file to patch an ebuild. |
| 29 |
Either edit the ebuild directly and add your patch or open a bug |
| 30 |
asking the toolchain maintainers to add epatch_user to gcc. But I have |
| 31 |
to say, it is easier if you just edit the ebuild, add the epatch_user |
| 32 |
line there, run ebuild digest and then place your patch in |
| 33 |
/etc/portage/patches. You should then be able to build gcc just fine. |
| 34 |
|
| 35 |
-- |
| 36 |
Regards, |
| 37 |
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
Archives