On 2018-04-06 11:54 +0200, to...@tuxteam.de wrote:
> On Thu, Apr 05, 2018 at 05:46:18PM +0200, Helmut Grohne wrote:
> 
> > I think this warning is obsolete as we assume that the packaging sets up
> > CC. For most cases, it actually happens automatically:
> >  * dh_auto_build passes it to make.
> >  * If you include /usr/share/dpkg/buildtools.mk in debian/rules, it'll
> >    be correct.
> 
> Hm. I can't find that file. Apt-file (and packages.debian.org) can't
> either?

It's part of dpkg-dev (but was typoed: /usr/share/dpkg/buildflags.mk )

> >  * For many build systems, setting CC is not necessary and
> >    dh_auto_configure does the right thing anyway.
> 
> Yes, but how do I find out why it is failing in my case?

Is it actually failing if you don't set CC: or is it just spitting out
a confusing message?

Setting DH_VERBOSE can help, or using make -d (or see man make '-debug' for
more details). To see when the message is being issued. 

> the build system *was* using the wrong compiler, i.e. x86_64 instead
> of armhf.

OK, so that's a useful error then? Is the problem that it's not gone
away now that you are in fact setting the right one? It should do (and
just did in my quick test). But I guess if the arch is set first, and
CC later (as is probably normal in most rules files driven by
dpkg-buildpackage -a) then you will always see this warning, where
it's not really very helpful.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to