On Tue, Apr 07, 2009 at 04:33:19PM -0300, Ricardo Augusto de Souza wrote:
> OK.
> I AM currently running         $ cd /sys/arch/${ARCH}/conf
> 
>      Edit the kernel configuration file.  ${NAME} is your kernel configuration
>      file.  You should not edit GENERIC; create your own kernel configuration
>      if you need to make modifications.  If using GENERIC you can skip this
>      step.  And yes, you may use vi(1), mg(1), or any other editor you choose.
> 
>            $ vi ${NAME}
> 
>      Build the kernel compilation directory and compile the kernel:
> 
>            $ config ${NAME}
>            $ cd ../compile/${NAME}
>            $ make clean && make depend && make

That is just the kernel that you will run on the system that you
use to compile the release.
I am assuming that you are compiling the release on a box that does
need aac. So you don't need a custom kernel in that step.

However, you need to customize GENERIC and RAMDISK_CD during this step:

   4. Make and validate the system release
     The system release consists of at least one generic kernel, some instal-
     lation media, the release `tarballs', installation instructions, and
     checksum files.

     <snip>

Before you run the followoing commands, you edit the GENERIC and
RAMDISK_CD configs to add aac support.

     Check that the contents of ${DESTDIR} pretty much match the contents of
     the release `tarballs':

           # cd /usr/src/etc && nice make release
           # cd /usr/src/distrib/sets && sh checkflist
           # unset RELEASEDIR DESTDIR

The first of those commands will compile the kernels used for the install
media and it will compile the kernel the installed system will run.
It's those kernels that need aac.

Stefan

Reply via email to