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 ebehar
Recipients benjamin.peterson, brett.cannon, brodie, ebehar, erickt, mark.dickinson, rpetrov, tarek
Date 2009-06-02.22:46:11
SpamBayes Score 8.107971e-06
Marked as misclassified No
Message-id <1243982774.56.0.050517109456.issue6154@psf.upfronthosting.co.za>
In-reply-to
Content
I think I've found the problem.

In configure:

  13830 if test "${ac_cv_lib_intl_textdomain+set}" = set; then
  13831   echo $ECHO_N "(cached) $ECHO_C" >&6
  13832 else
  13833   ac_check_lib_save_LIBS=$LIBS
  13834 LIBS="-lintl  $LIBS"

but then 

  13883 rm -f core conftest.err conftest.$ac_objext
conftest_ipa8_conftest.oo \
  13884       conftest$ac_exeext conftest.$ac_ext
  13885 LIBS=$ac_check_lib_save_LIBS

ac_check_lib_save_LIBS is assigned before -lintl is added to LIBS, and
then LIBS is unconditionally re-assigned to ac_check_lib_save_LIBS a
little bit further down, which then doesn't have -lintl in it.

I've included a patch that changes this to be:

  ...

  13880         ac_cv_lib_intl_textdomain=no
  13881         LIBS=$ac_check_lib_save_LIBS
  13882 fi
  13883 
  13884 rm -f core conftest.err conftest.$ac_objext
conftest_ipa8_conftest.oo \
  13885       conftest$ac_exeext conftest.$ac_ext
  13886 fi

So that LIBS is only restored to the saved state if the check fails.

I'm not sure if mucking with the configure file directly is a great
idea, but this was the simplest thing I could think of that would work.
History
Date User Action Args
2009-06-02 22:46:14ebeharsetrecipients: + ebehar, brett.cannon, mark.dickinson, benjamin.peterson, erickt, tarek, brodie, rpetrov
2009-06-02 22:46:14ebeharsetmessageid: <1243982774.56.0.050517109456.issue6154@psf.upfronthosting.co.za>
2009-06-02 22:46:12ebeharlinkissue6154 messages
2009-06-02 22:46:12ebeharcreate