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 loewis
Recipients
Date 2005-09-29.16:06:04
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=21627

I'm hesitant to add instructions to the README of the style
"do this to get it work", especially when I believe these
instructions are either wrong or overspecified. Adding
something like "Jone Stone <jestone@users.sf.net> suggests
to use these options" might be a compromise.

As for why --without-gcc causes dropping of compiler flags:
It's because of this fragment of configure.in:

AC_MSG_CHECKING(for --without-gcc)
AC_ARG_WITH(gcc,
            AC_HELP_STRING(--without-gcc,never use gcc),
[
        case $withval in
        no)     CC=cc
                without_gcc=yes;;

Not sure what caused the introduction of this fragment, but
omitting --without-gcc looks like the right thing to do.

In general, I would much more prefer to receive patches that
make things work out of the box, instead of documenting bugs.
History
Date User Action Args
2008-01-20 09:58:11adminlinkissue1306248 messages
2008-01-20 09:58:11admincreate