[Python-bugs-list] [ python-Bugs-702147 ] --without-cxx flag of configure isn't documented.

SourceForge.net noreply@sourceforge.net
Mon, 17 Mar 2003 03:49:06 -0800


Bugs item #702147, was opened at 2003-03-12 12:05
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=702147&group_id=5470

Category: Documentation
Group: Python 2.2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: J.A. Schonekerl (jschonek2)
Assigned to: Nobody/Anonymous (nobody)
Summary: --without-cxx flag of configure isn't documented.

Initial Comment:
Hi,

I can't any discription of the --without-cxx for configure.
If you do a ./configure --help it simply doesn't show up!

And let this be the flag I needed to build python without
libstdc++!

Best regards,

Jan

----------------------------------------------------------------------

>Comment By: J.A. Schonekerl (jschonek2)
Date: 2003-03-17 11:49

Message:
Logged In: YES 
user_id=732192


For me it wasn't clear why the libstdc++ library was dynamicaly 
linked into the python interpreter. I could not find the
relation 
between the --with-cxx=<compiler> flag and the libstdc++
library. The README file tells something about the --with-cxx
flag. But not that this causes the libstdc++ inclusion (not
everyone is C/C++ expert). Afther reading the README file it's
also not logical why --with-cxx is choosen as default.

Another problem a had:
I'am missing the default settings with the --with/--wthout and 
--disable/--enable settings, or are all settings listed under 
"--enable and --with options recognized:" in the configure
output defaults? 
Maybe this info should be added the same way as this line
from the configure output.
"Options: [defaults in brackets after descriptions]".

I have these points for improvement:

- Make clear in the README file, with the --with-cxx
explenation that this causes libstdc++ inclusion.

- Make clear in the configure output that all listed
--with/--without/--enable/--disable flags are the default (mmm,
this sounds logical for me now...).

- Make clear in the configure output that all listed
--with/--without/--enable/--disable flags have always a
oposite. (this sounds also logical now, they're all bools....).

- Why is --with-cxx choosen as default, the README file
suggests that you only want this if..............

I'am not a ./configure or c++ expert, maybe my points are
logical
and normal behaviour for you. But I'am sure they will help
other poeple that arn't expert either.

And yes I can make a patch for these points.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2003-03-15 13:33

Message:
Logged In: YES 
user_id=21627

This is a general configure principle: For every --with
option, it is possible to pass --without, and for every
--enable option, it is posible to pass --disable.

Would you be willing to create a patch that explains this to
the user in a way that you would understand?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=702147&group_id=5470