| 1 |
I tried rebuilding bash natively, and still had the same error with |
| 2 |
epatch & bash signals. |
| 3 |
|
| 4 |
After checking out the ebuild, the following line helped guide me: |
| 5 |
|
| 6 |
# Don't barf on handled signals in scripts |
| 7 |
epatch "${FILESDIR}"/${PN}-3.0-trap-fg-signals.patch |
| 8 |
|
| 9 |
I'll apply this patch doing a manual build and see how it goes. |
| 10 |
|
| 11 |
~/Chris |
| 12 |
|
| 13 |
Mike Frysinger wrote: |
| 14 |
> On Thursday 10 January 2008, Mike Frysinger wrote: |
| 15 |
>> On Thursday 10 January 2008, Christopher Friedt wrote: |
| 16 |
>>> I ran into this really strange epatch failure recently with an |
| 17 |
>>> arm-softfloat-linux-gnu system. I originally cross-compiled/emerged the |
| 18 |
>>> baselayout, libc, gcc, etc, and now I'm natively compiling / emerging |
| 19 |
>>> other packages with qemu. |
| 20 |
>>> |
| 21 |
>>> The strange thing, is that for generally any ebuild that uses epatch, |
| 22 |
>>> the patch fails. |
| 23 |
>> please review the FAQ. you need to build bash natively first or the |
| 24 |
>> signals are screwed up. |
| 25 |
> |
| 26 |
> blah, someone on irc pointed out the faq doesnt contain this question. seems |
| 27 |
> this local edit of mine was lost when my hd bit it. |
| 28 |
> |
| 29 |
> sorry about that, there should be a FAQ about this posted now. |
| 30 |
> |
| 31 |
> i did try to fix the issue once, but ended up fjucking bash for everyone, so |
| 32 |
> it was commented out. |
| 33 |
> -mike |
| 34 |
-- |
| 35 |
gentoo-embedded@l.g.o mailing list |
Archives