On Sun, Aug 07, 2005 at 11:11:56PM +0200, Martin v. Löwis wrote:
I've looked at the patch, and it looks fairly safe, so I committed it.
Thanks. I did not forget my promise to look into a more comprehensive
approach to the C++ build issues. But I first need to better understand the
potential
On Sun, Jul 17, 2005 at 04:01:20PM +1000, Anthony Baxter wrote:
On Saturday 16 July 2005 20:13, Christoph Ludwig wrote:
I submitted patch #1239112 that implements the test involving two TUs for
Python 2.4. I plan to work on a more comprehensive patch for Python 2.5 but
that will take some
On Tue, Jul 12, 2005 at 01:07:56AM +0200, Martin v. Löwis wrote:
Christoph Ludwig wrote:
Yes, but on ELF/Linux the default configuration should be --without-cxx
in the first place. If the build instructions make it sufficiently clear
that
you should prefer this configuration whenever
On Sun, Jul 10, 2005 at 09:45:25AM +0200, Martin v. Löwis wrote:
Christoph Ludwig wrote:
I'll describe it once more: *If* a program is compiled with the C++
compiler, is it *then* possible to still link it with the C compiler?
This is the question this test tries to answer.
The keyword
On Sun, Jul 10, 2005 at 09:35:33AM -0400, David Abrahams wrote:
Christoph Ludwig [EMAIL PROTECTED] writes:
I do not claim the 2 TUs test will cover all possible scenarios. I am not
even
sure this decision should be left to an automated test. Because if the test
breaks for some reason
On Sat, Jul 09, 2005 at 12:08:08AM +0200, Martin v. Löwis wrote:
David Abrahams wrote:
When I looked into this problem I saw that configure in fact builds a test
executable that included an object file compiled with g++. If the link step
with gcc succeeds then LINKCC is set as above, otherwise
