-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On Wed, Jun 17, 2009 at 10:32:01AM +0300, Martin-Éric Racine wrote: >On Sun, Jun 14, 2009 at 1:58 PM, Peter Eisentraut<[email protected]> 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 GNU software, autotools perform >>> these check for us and set CC=gcc autogamically. On other software, >>> CC is often left unset. This is mostly okay on a Debian system, >>> because the presumption is that CC=gcc, but we can never be sure of >>> what parallel compilers, etc. someone might run, so it would be >>> desirable for class/langcore.mk to set CC=gcc is it is unset. >> >> Do you have a concrete counterexample where the current code does not >> work? > >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 options. >However, class/langcore.mk includes GNU-specific options without >checking that the compiler supports them (or at least setting CC=gcc >to ensure that it does), so the build is not guaranteed to succeed.
Such environment is not a standard build environment, I believe. You are welcome to try stress-testing cdbs in environments other than plain Debian (e.g. with different C compilers installed and preferred in $PATH), but really it is not a bug if such experiments fail. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAko4s9gACgkQn7DbMsAkQLjHwgCghofrGPCttsOywary09+gSf3e xTgAoKGBFvaXrdZSzL166eNHpLPUObXd =8cc7 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
