Hi Chris,
Chris Gianelloni wrote:
[...] Remember that everything
done within catalyst is downloaded/compiled by catalyst. So
genkernel/splashutils, etc all come from *inside* the chroot, which will
*always* be Gentoo if using a Gentoo stage tarball, even if you're
running on Debian or Fedora as your host.
Thank you for pointing that out :)
Using catalyst on debian would be as simple as this:
tar -cxjf catalyst-1.1.10.10.tar.bz2 -C /usr/lib
mkdir -p /etc/catalyst
cp /usr/lib/catalyst/files/catalyst.conf /etc/catalyst
I will include it in the howto.
As for distcc, it works perfectly fine with cross-compiling.
See my bug under
http://bugs.gentoo.org/show_bug.cgi?id=103493
I'm just telling about my experiences. That bug didn't get any attention
yet, although I could easily reproduce it.
Yeah, it's your toolchain causing the issue. It works fine with a
proper cross-compiler, as I stated.
How do I turn my gcc into a 'proper cross-compiler' and get a correct
toolchain? Is it sufficient to include these two lines in
/etc/portage/package.use:
sys-devel/distcc crosscompile
sys-devel/binutils multitarget
and in /etc/portage/package.keywords
sys-devel/distcc ~x86
and re-emerge distcc and binutils? I will include that information in my
bug and close it ;)
[...] Does it matter if there's an RPM? I honestly don't know, as I compiled
my own RPM.
Doesn't matter. If it's needed, someone will build one.
Thanks for your help,
Georg
| 
