Re: Isn't cc the default compiler?

[Raul Miller <rdm@test.legislate.com>]

jdassen@wi.leidenuniv.nl <jdassen@wi.leidenuniv.nl> wrote:
> The alternatives mechanism is used for _local_ settings. Determining
> the compiler with which packages are built is IMO not a local issue,
> and should not be left up to the local system administrator.
>
> IMO, packages should use "CC = gcc" and "CXX = g++" unless this breaks
> the package (e.g. some packages combine C and C++ code; there C code
> should therefore be compiled with CC = egcc on architectures where GNU
> gcc is the primary compiler).

I believe that where feasible, we should live with the defaults provide.

I think the only context where it's appropriate for us to specify
the compiler (other than where the defaults would break the upstream
package) is in the context of a generic debian build environment.
We need an environment where we can just type "make" (or something
equivalent) and have it build an entire distribution -- in that context,
it's reasonable to specify the compiler (and it's reasonable to document
the environment so the choice can be mimiced elsewhere).

It may be reasonable to strip out an upstream definition of CC, but this
would have to be done carefully.

Any other choice makes porting needlessly hard.

-- 
Raul


--  
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org