Author ngie
Recipients goertzen, gregory.p.smith, hugo_koopmans, jdalambert, jepler, mattcomms, ngie, nico0438, nico38, robsa, rpetrov, solarx, theller, vapier, xudong888
Date 2009-10-31.22:53:03
SpamBayes Score 1.2033e-05
Marked as misclassified No
Message-id <1257029585.26.0.661506053502.issue1006238@psf.upfronthosting.co.za>
In-reply-to
Content
I'm trying to resolve this issue on:

2.6-releasemaint
trunk
3.1-releasemaint
py3k

first by resolving issues configure.in, but there are a TON of
AC_TRY_RUN's, which means that this code cannot be cross-compiled as-is
(25 on 2.x -- 27 on 3.x).

Is requiring the end-user to define the autoconf variables appropriately
to their platform when running configure (when provided an error message
telling them so), a longterm sustainable requirement? I know it isn't as
user friendly, but this is a definite problem that either needs to be
fixed in the autoconf tests (if possible) or the C code itself.

I wouldn't mind updating the INSTALL or README files to reflect this
change either, if needed.
History
Date User Action Args
2009-10-31 22:53:05ngiesetrecipients: + ngie, jepler, theller, gregory.p.smith, goertzen, jdalambert, vapier, solarx, robsa, xudong888, nico38, nico0438, hugo_koopmans, mattcomms, rpetrov
2009-10-31 22:53:05ngiesetmessageid: <1257029585.26.0.661506053502.issue1006238@psf.upfronthosting.co.za>
2009-10-31 22:53:04ngielinkissue1006238 messages
2009-10-31 22:53:03ngiecreate