Tomasz Mloduchowski wrote:
Now, that I've got your attention. IMHO above should NOT fail - most of
the software in portage is already using ${HOST}-gcc instead and gcc
symlink is just a convenience.
But it does. In packages I will never suspect being nasty (qt, lynx) and
ones I would, but they shouldn't (fuse)
What is so important in that feature? Crosscompilation and distcc.
For example, I have alpha-unknown-linux-gnu running as a distcc server
for x86 box. And, it does not work for those packages.
I got sick of filling 3 almost identical bug reports
110040, 110086 and 110087 and I'm not even at half of emerge -uD world.
So, if you agree that it IS a problem, do the `rm` and run ebuilds you
maintain. You will save me another 10 or so unnended bugreports.
Tomasz
You can quite easily get around these problems by being clever with
distccd and some strategically placed symlinks. Simply, cd
/usr/<foo>-unknown-linux-gnu/gcc-bin/<version>/, create symlinks in that
directory that point cc, gcc, g++, and c++ to the appropriate
${CHOST}-gcc, etc... binaries, and then use a script such as
http://dev.gentoo.org/~geoman/mips-distcc.sh to start an arch specific
distccd on its own port. You can then use distcc-config to set your
distcc hosts to host:port on the box you are compiling on.
This works great, and is pretty much 100% foolproof as far as I can tell.
-Steve
--
gentoo-dev@gentoo.org mailing list
