Architectures

From RockWiki

Jump to: navigation, search

Architectures

Aside from the fact that each architecture needs at least to register itself to the ROCK Linux build system, it might provide patches and kernel configuration to work properly.

The registering works via the preconfig.in file - just like for the targets:

 CFGTEMP_ARCHLIST="$CFGTEMP_ARCHLIST arch_name4 Long_Visible_Name"

The usual config.in can be used to force options to be set/unset or to introduce new options (just like the config.in in several other places).

The file gcc-options controls additional options passed to GCC.

The files kernel{$treever,}.conf{m4,sh,} and kernel-disable{treever,}.lst are used to control the options used for the linux kernel build.

As already mentioned in the explanation of packages, architecture specific patches are added to the respective package with a patch.$arch suffix.

A archtest.out or archtest.sh file should be present to define some constants like:

arch_sizeof_short=2
arch_sizeof_int=4
arch_sizeof_long=4
arch_sizeof_long_long=8
arch_sizeof_char_p=4
arch_bigendian=yes
arch_machine=powerpc
arch_target=powerpc-unknown-linux-gnu
Personal tools