> >> 1.) Is there any dependency to hardware in the Argyll code (x86, ppc, ...)? > >Yes there is. There are both endian dependent and platform >dependent code. This is either handled automatically, or >with the appropriate platform #define. The appropriate >defines are either part of the platform, or some of the >Jamfiles have platform build dependencies defined >in the Jambase. As Gentoo uses a BSD-like layout but a Linux-Kernel, I'm referring to the autotools version. Gentoo supports the following platforms: alpha amd64 arm hppa ia64 m68k mips ppc ppc64 ppc-macos s390 sh sparc x86 In the Gentoo installation-packages (ebuilds), such a keyword shows if the package supports that platform. A preceding '~' marks the package being in a testing state for that platform, while a '-' marks it as non-working. e.g. "x86" means it's in a working state on the x86 platform "~x86" means it's in a testing state on the x86 platform "-x86" means it is not working on the x86 platform Which platforms does autotools-argyll support in the three states? >> 2.) Is autotools_argyll FHS 2.0 compliant? > >Sorry, I've no idea what FHS 2.0 is. It's the "Filesystem Hierarchy Standard". Please see http://www.pathname.com/fhs for further information. According to Alastair it seems to be compliant. All the best, Rene Bartsch