1 |
On 31-07-2009 15:03:25 +0100, Alan Hourihane wrote: |
2 |
> Can we finally get rid of the horrible GCC kludge for the symlink issue |
3 |
> in the eclass ? |
4 |
> |
5 |
> Or at the very least provide a flag in which I can turn it off without |
6 |
> having the need to go poking eclass everytime I've re-synced ? |
7 |
|
8 |
how about this compromise? |
9 |
|
10 |
@@ -19,7 +19,7 @@ |
11 |
toolchain_pkg_setup() { |
12 |
# yuck, but how else to do it portable? |
13 |
local realEPREFIX=$(python -c 'import os; print os.path.realpath("'"${EPREFIX}"'")') |
14 |
- if [[ ${EPREFIX} != ${realEPREFIX} ]] ; then |
15 |
+ if [[ -z ${I_KNOW_MY_GCC_WORKS_FINE_WITH_SYMLINKS} && ${EPREFIX} != ${realEPREFIX} ]] ; then |
16 |
ewarn "Your \${EPREFIX} contains one or more symlinks. GCC has a" |
17 |
ewarn "bug which prevents it from working properly when there are" |
18 |
ewarn "symlinks in your \${EPREFIX}." |
19 |
|
20 |
|
21 |
-- |
22 |
Fabian Groffen |
23 |
Gentoo on a different level |