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 bobatkins
Recipients bobatkins, loewis, sergiodj, spacey
Date 2008-06-05.19:28:16
SpamBayes Score 0.000967835
Marked as misclassified No
Message-id <48483E4D.2000701@digilink.net>
In-reply-to <484839A5.1090305@v.loewis.de>
Content
Martin,

Your method is just flat wrong - equivalent to using a sledgehammer. The 
libraries fail to link not because gcc install is wrong but because the 
-m64 flag needs to be passed to the linker. Your method just fixes the 
compilation stage. You are blaming the gcc installation for your problem 
when in fact the /_*rest*_/ of the open source world builds just fine 
using gcc when the proper flags are passed at the proper stages of the 
build.

This situation is so sad to see. This isn't the way open source 
development is supposed to be. Basically _/*you*/_ alone are the 
gatekeeper and you are refusing to deal with what is a very simple problem.

To be sure I really don't care anymore - we will continue to apply the 
patches that we have to fix the build problem however, we will also 
actively discourage the use of Python for our customers and all future 
development/deployment since it is obvious that as the maintainer you 
are completely closed minded and uncooperative when it comes to fixing 
things.

My suggestion for the rest of the Python community is to branch and 
re-host the Python project elsewhere if anyone wants to see it move forward.
Files
File name Uploaded
DigiLink_esig_logo.jpg bobatkins, 2008-06-05.19:28:16
unnamed bobatkins, 2008-06-05.19:28:14
History
Date User Action Args
2008-06-05 19:28:18bobatkinssetspambayes_score: 0.000967835 -> 0.000967835
recipients: + bobatkins, loewis, sergiodj, spacey
2008-06-05 19:28:17bobatkinslinkissue1628484 messages
2008-06-05 19:28:17bobatkinscreate