Re: Consistent handling of the DEB_BUILD_OPTIONS
Miriam Ruiz wrote:
> 2007/11/6, Neil Williams <email@example.com>:
>> There needs to be some agreement on what nocheck or notest means and
>> which one to use. For Emdebian needs, whichever name is used, the
>> imperative is that setting that DEB_BUILD_OPTION *must* completely
>> prevent the execution of any compiled program within any test suite
>> provided by upstream. The only checks or tests that can be implemented
>> outside nocheck|notest must only use system binaries from coreutils,
>> binutils-multiarch or one of the gcc binaries.
> Some software packages, such as libcap, for example, seem to depend on
> some code being autogenerated from a program executed in the target
> (in this case, the generation of cap_names.h).
Is this file architecture dependent? If not, one could build everything
to generate the file and rebuild it later for the targeted architecture,
using the file which was generated before. Sounds ugly, but it should work.