This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients bobatkins, jackjansen, jprante, lemburg, loewis, pitrou, ronaldoussoren, rpetrov, sergiodj, skrah, spacey
Date 2010-01-27.12:54:41
SpamBayes Score 1.11022e-16
Marked as misclassified No
Message-id <4B60378F.3040602@egenix.com>
In-reply-to <1264594761.45.0.743158697812.issue1628484@psf.upfronthosting.co.za>
Content
Stefan Krah wrote:
> 
> Stefan Krah <stefan-usenet@bytereef.org> added the comment:
> 
> The builds are almost identical, so I attach a diff of the build output.
> For both builds, I used a fresh Python-3.1.1 directory. This looks
> suspicious:
> 
> -checking whether va_list is an array... yes
> +checking whether va_list is an array... no
> 
> 
> For completeness' sake: "-fno-strict-aliasing -m32" were reversed in the
> BASECFLAGS case, so I edited the BASECFLAGS output for the purposes of
> creating a diff.

Thanks.

Looking at the diff I cannot see any difference between the
two builds in terms of gcc options applied during the compile
and link step.

As you noticed, this leaves the va_list difference which also
causes the warnings in the 32-bit build.

I guess this points to the real cause of the problem: configure
doesn't know anything about BASECFLAGS, but does use CFLAGS for
checking various compiler features, so Antoines command line
options using CFLAGS work, while the ones I posted don't.
History
Date User Action Args
2010-01-27 12:54:44lemburgsetrecipients: + lemburg, loewis, jackjansen, ronaldoussoren, pitrou, bobatkins, sergiodj, spacey, rpetrov, jprante, skrah
2010-01-27 12:54:42lemburglinkissue1628484 messages
2010-01-27 12:54:41lemburgcreate