-----BEGIN PGP SIGNED MESSAGE-----
On Wed, Apr 11, 2018 at 05:31:15PM +0100, Wookey wrote:
> On 2018-04-06 11:54 +0200, to...@tuxteam.de wrote:
> > 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 )
Thanks. This one shows on my radar :-)
> > > * 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?
I somehow dreamt it failed: it didn't (I already retracted in another mail).
> 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.
But thanks for that: duly noted.
> > 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.
No: the "wrong compiler" problem disappeared, so I assume I was doing
something wrong. As far as I am concerned, the error isn't useful
Thanks a lot for your help!
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----