Re: Bizarre and provocatively irritating cpantester reports

I put it through some encoding fixing routines and came out with this:

GMPz.xs: In function ‘Rmpz_cdiv_q_2exp’:
GMPz.xs:489: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs:489: error: (Each undeclared identifier is reported only once
GMPz.xs:489: error: for each function it appears in.)
GMPz.xs: In function ‘Rmpz_cdiv_r_2exp’:
GMPz.xs:493: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs: In function ‘Rmpz_scan0’:
GMPz.xs:861: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs: In function ‘Rmpz_scan1’:
GMPz.xs:865: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs: In function ‘Rmpz_setbit’:
GMPz.xs:869: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs: In function ‘Rmpz_clrbit’:
GMPz.xs:873: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs: In function ‘Rmpz_tstbit’:
GMPz.xs:877: error: ‘mp_bitcnt_t’ undeclared (first use in this functi
+on)
GMPz.xs: In function ‘Rmpz_combit’:
GMPz.xs:1297: error: ‘mp_bitcnt_t’ undeclared (first use in this funct
+ion)
[download]

It appears to be ISO-8859-1 misconfigured in headers as UTF-8 or something similar.

Comment on Re: Bizarre and provocatively irritating cpantester reports Download Code

Replies are listed 'Best First'.
Re^2: Bizarre and provocatively irritating cpantester reports by syphilis (Archbishop) on Apr 22, 2015 at 02:14 UTC
Ok ... I take it that once I've removed the misleading bullshit, I can then regard what's left as reflecting the actual problem. And I guess the best way to stop the abuse is to simply fix that actual underlying problem. Thanks salva, mr_mischief. Cheers, Rob	[reply]