| 1 |
> |
| 2 |
> I was reading this: |
| 3 |
> |
| 4 |
> http://www.gentoo.org/doc/en/cross-compiling-distcc.xml |
| 5 |
I also read it far before I wrote my email. |
| 6 |
|
| 7 |
> |
| 8 |
> It specifically mentions you need crossdev: |
| 9 |
> |
| 10 |
> If you are cross-compiling between different subarchitectures |
| 11 |
> for Intel x86 (e.g. i586 and i686), you must still build a full |
| 12 |
> cross-toolchain for the desired CHOST, or else the compilation |
| 13 |
> will fail. |
| 14 |
> |
| 15 |
> I suppose any cross compiler might be enough and you don't need |
| 16 |
> crossdev. I don't know. |
| 17 |
I need to repeat: The other nodes are all running Debian and there is *no* crossdev package. And I wrote in my initial mail, that I was already able to cross-compile other Gentoo packages on these nodes as the parameters -m32 and -march=i686 were *provided* by those packages which seems to be *not* the case with e.g. klibc |
| 18 |
|
| 19 |
All I want is that the klibc package is honoring the global CFLAGS or else I have to temporary disable distcc (FEATURES variable needs to be commented out) for klibc, emerge klibc and then re-enable distcc to have a great speedup for other packages (that are honoring CFLAGS from make.conf). |
| 20 |
|
| 21 |
I do that now what I wrote but it is really annoying to cannot leave the compilation unattended. I repeat once more: cross-compiling is possible on my nodes, so there is absolutely no need to setup such "cross-toolchains" because it works. |
Archives