proxycheck FTCBFS due to it using a home-grown configure script
with non standard options without a configure.ac

as it seems, it is not really possible to replace this with debhelper
tooling and hence right CC should be passed in d/rules.

along with this, it tries to run sample programs in configure just
to check the compiler works. this in principle serves no real
functionality and converting them to compile checks is enough.

a patch is attached with these changes. please consider applying.

Hi Nilesh,

A minor detail. I later noticed that a number of your bugs are assigned
to binary packages rather than source packages. The interpretation of
crossqa.d.n is that when you assign to a binary package it is the
package that causes the problem and the affected source packages are the
ones failing to cross build. In your cases, there typically are no
affected source packages and hence your bug reports do not get
associated in the crossqa.d.n web view.

Could you change the way you report cross build bugs to use either
"Package: src:proxycheck" or "Source: proxycheck"?

The bug importer presently complains about the following bugs not
affecting any source packages (not all of them due to you). Would you
like to reassign them to source packages?

#1106652
#1106653
#1106703
#1110270
#1110295
#1110312
#1110314
#1110323
#1110332
#1110345
#1110406
#1110487
#1110492
#1111113
#1111725

Helmut

Oh man. This is annoying but I understand the reasoning.
Could you please consider to document this somewhere?

Will do so in future bug reports.

Adjusted all.

Best,
Nilesh

Hi Nilesh,

I'm not sure where to document that, but for the related "ftbfs" tag
(not usertag), it is documented at
https://www.debian.org/Bugs/Developer#tags and ftcbfs caries over those
semantics.

Thank you.

Helmut