Martin v. Löwis <[EMAIL PROTECTED]> added the comment: > 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.
And indeed, the flag *is* passed to the linker. Python links with CC unless specified otherwise, which will be "gcc -m64". That ought to work, and it does work when linking Python itself. > Your method just fixes the compilation stage. Not true. > 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. I'm sorry you feel that way. Feel free to bring up the issue on python-dev if you think you are being ignored. I assure you this is not the case - but I want to see the problem first before accepting fixes. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1628484> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
