| 1 |
May I ask whether the bug only happens when the symlink to gcc is removed ? |
| 2 |
So using $EPREFIX with symlinks will be of no problem while the |
| 3 |
$EPREFIX keeps the same, right ? |
| 4 |
|
| 5 |
2009/7/31 Alan Hourihane <alanh@×××××××××××.uk>: |
| 6 |
> On Fri, 2009-07-31 at 17:11 +0200, Fabian Groffen wrote: |
| 7 |
>> On 31-07-2009 16:09:34 +0100, Alan Hourihane wrote: |
| 8 |
>> > On Fri, 2009-07-31 at 17:01 +0200, Fabian Groffen wrote: |
| 9 |
>> > > can you be a bit more explanatory on what this is about exactly? |
| 10 |
>> > |
| 11 |
>> > This mess, and the associated code in toolchain.eclass..... |
| 12 |
>> > |
| 13 |
>> > if [[ ${EPREFIX} != ${realEPREFIX} ]] ; then |
| 14 |
>> > ewarn "Your \${EPREFIX} contains one or more symlinks. |
| 15 |
>> > GCC has |
| 16 |
>> > a" |
| 17 |
>> > ewarn "bug which prevents it from working properly when |
| 18 |
>> > there ar |
| 19 |
>> > e" |
| 20 |
>> > ewarn "symlinks in your \${EPREFIX}." |
| 21 |
>> > ewarn "See |
| 22 |
>> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29831" |
| 23 |
>> > ewarn "Continuing with your EPREFIX set to:" |
| 24 |
>> > ewarn "${realEPREFIX}" |
| 25 |
>> > export EPREFIX=${realEPREFIX} |
| 26 |
>> > fi |
| 27 |
>> |
| 28 |
>> I guess the problem is that it works for you but breaks for others? |
| 29 |
> |
| 30 |
> It's fine here. |
| 31 |
> |
| 32 |
> At least a variable to turn it off would be useful. |
| 33 |
> |
| 34 |
> Alan. |
| 35 |
> |
| 36 |
> |
| 37 |
> |
Archives