1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 06/25/14 04:27, Rick "Zero_Chaos" Farina wrote: |
5 |
> |
6 |
> It kinda looks to me like you are abusing --kernel--cc for |
7 |
> something it's not meant for, which makes me think the "fix" is |
8 |
> either doing it right, or fixing genkernel. If you can work up a |
9 |
> sane patch I'll drop it in genkernel myself, but please hit me |
10 |
> directly or I'll completely miss it. |
11 |
> |
12 |
> Thanks, Zero |
13 |
> |
14 |
> |
15 |
|
16 |
Regarding doing it right, let me explain why we're doing it that way, |
17 |
maybe we can find some other way to do it correctly. |
18 |
|
19 |
The ppc installcd has multiple kernels for different type of machines, |
20 |
it has exactly 3 types of kernels, 2 64bit and 1 32bit. It uses a |
21 |
stage3 ppc64 32ul to build the cd. Until last year ppc64 32ul used an |
22 |
independent gcc(kgcc64) to build the kernel, so it could be called |
23 |
with powerpc64-unknown-... to build the kernel. |
24 |
|
25 |
However it switched to using a multilib gcc, so for building a 64bit |
26 |
kernel it can use -m64. |
27 |
|
28 |
gitweb for overlays is still down, so i can't post the link to the |
29 |
spec file, but its this spec file: |
30 |
releases/weekly/specs/ppc/ppc64/installcd-stage2-minimal.spec |
31 |
|
32 |
Any suggestions are welcome. |
33 |
-----BEGIN PGP SIGNATURE----- |
34 |
Version: GnuPG v2.0.19 (GNU/Linux) |
35 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
36 |
|
37 |
iEYEARECAAYFAlQSkkgACgkQuQc30/atMkAwUACfT24Rx1yvFKkuq+RQHBYUmfOL |
38 |
ohsAn0pRmVh0ob2EgSHLfUF4SSgwBLYj |
39 |
=DVnG |
40 |
-----END PGP SIGNATURE----- |