2009/6/17 Martin-Éric Racine :
> In the case where an upstream tarball comes with a single C file and
> no Makefile, the only option a maintainer has is to create a manual
> build target in debian/rules to compile the binary and to include
> class/langcore.mk to always use the standard Debian build
On Wednesday 17 June 2009 10:32:01 Martin-Éric Racine wrote:
> On Sun, Jun 14, 2009 at 1:58 PM, Peter Eisentraut wrote:
> > On Sunday 22 June 2008 18:11:39 Martin-Éric Racine wrote:
> >> class/langcore.mk sets -g -Wall -O2 without checking whether CC can
> >> actualy process these options. For inst
On Sun, Jun 14, 2009 at 1:58 PM, Peter Eisentraut wrote:
> On Sunday 22 June 2008 18:11:39 Martin-Éric Racine wrote:
>> class/langcore.mk sets -g -Wall -O2 without checking whether CC can actualy
>> process these options. For instance, -g produces output that is partially
>> GDB-specific. On most G
On Sunday 22 June 2008 18:11:39 Martin-Éric Racine wrote:
> class/langcore.mk sets -g -Wall -O2 without checking whether CC can actualy
> process these options. For instance, -g produces output that is partially
> GDB-specific. On most GNU software, autotools perform these check for us
> and set CC
4 matches
Mail list logo
