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