1 |
Hi Chris, |
2 |
|
3 |
Chris Gianelloni wrote: |
4 |
> [...] Remember that everything |
5 |
> done within catalyst is downloaded/compiled by catalyst. So |
6 |
> genkernel/splashutils, etc all come from *inside* the chroot, which will |
7 |
> *always* be Gentoo if using a Gentoo stage tarball, even if you're |
8 |
> running on Debian or Fedora as your host. |
9 |
|
10 |
Thank you for pointing that out :) |
11 |
|
12 |
> Using catalyst on debian would be as simple as this: |
13 |
> |
14 |
> tar -cxjf catalyst-1.1.10.10.tar.bz2 -C /usr/lib |
15 |
> mkdir -p /etc/catalyst |
16 |
> cp /usr/lib/catalyst/files/catalyst.conf /etc/catalyst |
17 |
|
18 |
I will include it in the howto. |
19 |
|
20 |
>>>As for distcc, it works perfectly fine with cross-compiling. |
21 |
>> |
22 |
>>See my bug under |
23 |
>> |
24 |
>>http://bugs.gentoo.org/show_bug.cgi?id=103493 |
25 |
>> |
26 |
>>I'm just telling about my experiences. That bug didn't get any attention |
27 |
>>yet, although I could easily reproduce it. |
28 |
> |
29 |
> |
30 |
> Yeah, it's your toolchain causing the issue. It works fine with a |
31 |
> proper cross-compiler, as I stated. |
32 |
|
33 |
How do I turn my gcc into a 'proper cross-compiler' and get a correct |
34 |
toolchain? Is it sufficient to include these two lines in |
35 |
/etc/portage/package.use: |
36 |
|
37 |
sys-devel/distcc crosscompile |
38 |
sys-devel/binutils multitarget |
39 |
|
40 |
and in /etc/portage/package.keywords |
41 |
|
42 |
sys-devel/distcc ~x86 |
43 |
|
44 |
and re-emerge distcc and binutils? I will include that information in my |
45 |
bug and close it ;) |
46 |
|
47 |
> [...] Does it matter if there's an RPM? I honestly don't know, as I compiled |
48 |
> my own RPM. |
49 |
|
50 |
Doesn't matter. If it's needed, someone will build one. |
51 |
|
52 |
Thanks for your help, |
53 |
|
54 |
Georg |
55 |
-- |
56 |
gentoo-catalyst@g.o mailing list |