| 1 |
* Marcio Luis Teixeira [marciot@×××××××××××××××.edu] [2002-10-19 14:40 -0600]: |
| 2 |
|
| 3 |
> I have a question, what's special about "sys-kernel/ppc-sources"? I |
| 4 |
> though all architetures used a common kernel source tree and the the |
| 5 |
> configuration/compilation stage would do the right thing. |
| 6 |
|
| 7 |
We do use a common kernel source tree (kernel.org) but patches are |
| 8 |
applied dependent on what sys-kernel/* is merged. ppc-sources are |
| 9 |
specific to ppc. sys-kernel/gentoo-sources (and others in sys-kernel) |
| 10 |
have a number of patches that will simply not work on ppc and so are |
| 11 |
kept as seperate ebuilds. |
| 12 |
|
| 13 |
> Anyhow, the reason I ask is that I want to enable IPSec support in my |
| 14 |
> kernel to run freeswan. Under the x86, I would have to "emerge |
| 15 |
> sys-kernel/crypto-sources" but this does not work on the PPC. |
| 16 |
|
| 17 |
gentoo-sources also contains the IPSec patches, as things stand there is |
| 18 |
no IPSec for ppc in sys-kernel/*. You might try to apply the patches |
| 19 |
from freeswan to ppc-sources but you may run into conflicts with |
| 20 |
previously applied patches. Please let us know how you get on. |
| 21 |
|
| 22 |
best |
| 23 |
|
| 24 |
cal |
Archives