Bob Atkins <[EMAIL PROTECTED]> added the comment: 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. Added file: http://bugs.python.org/file10524/unnamed Added file: http://bugs.python.org/file10525/DigiLink_esig_logo.jpg _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1628484> _______________________________________
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Martin,<br>
<br>
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 <i><u><b>rest</b></u></i> of the open source
world builds just fine using gcc when the proper flags are passed at
the proper stages of the build.<br>
<br>
This situation is so sad to see. This isn't the way open source
development is supposed to be. Basically <u><i><b>you</b></i></u>
alone are the gatekeeper and you are refusing to deal with what is a
very simple problem.<br>
<br>
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.<br>
<br>
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.<br>
<br>
-- <br>
<div class="moz-signature">
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<table border="0" cellpadding="2" cellspacing="0" width="569">
<tbody>
<tr bgcolor="#000099" valign="middle">
<td colspan="2"><font color="#ffffff"
face="Verdana, Arial, Helvetica, sans-serif" size="2"><strong>Bob
Atkins </strong></font><font color="#ffffff">Â </font></td>
</tr>
<tr valign="middle">
<td colspan="2"><font face="Verdana, Arial, Helvetica, sans-serif"
size="1"><em>President/CEO</em></font></td>
</tr>
<tr valign="middle">
<td width="233">
<p align="center"><font
face="Verdana, Arial, Helvetica, sans-serif" size="1"><b><font
color="#000080"><span
style="font-weight: bold; font-family: Trebuchet MS;"><a
href="http://www.digilink.net";><img
src="cid:part1.02060106.04080108@digilink.net" alt="DigiLink, Inc."
style="border: 0px solid ; width: 216px; height:
48px;"></a></span></font></b><br>
<font color="#006600">Business Inter-net-working</font><br>
<font color="#000099"><strong><em>The Cure for the Common
ISP!</em></strong></font></font></p>
</td>
<td width="328">
<p align="right"><font color="#666666"
face="Verdana, Arial, Helvetica, sans-serif" size="1">Phone: </font><font
face="Verdana, Arial, Helvetica, sans-serif" size="1">(310) 577-9450<br>
</font><font color="#666666"
face="Verdana, Arial, Helvetica, sans-serif" size="1">Fax: </font><font
face="Verdana, Arial, Helvetica, sans-serif" size="1">(310)
577-3360</font><font
face="Verdana, Arial, Helvetica, sans-serif" size="1"><br>
<font color="#666666">eMail:</font> <a class="moz-txt-link-abbreviated"
href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a><br>
</font></p>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<br>
Martin v. Löwis wrote:
<blockquote cite="mid:[EMAIL PROTECTED]" type="cite">
<pre wrap="">Martin v. Löwis <a class="moz-txt-link-rfc2396E"
href="mailto:[EMAIL PROTECTED]"><[EMAIL PROTECTED]></a> added the comment:
</pre>
<blockquote type="cite">
<pre wrap="">So, since this patch allows python to be built 64-bit on a
biarch
system, and without it, the build doesn't work
</pre>
</blockquote>
<pre wrap=""><!---->
This is simply not true. I can build Python 2.5 just fine for 64-bit
SPARC, using gcc, with
CC="gcc -m64" ./configure
make
Or, using SunPRO, with
CC="cc -m64" ./configure
make
I tested it myself, and it successfully builds a Python executable
(For gcc, the extension modules fail to load because it picks up
the wrong libgcc_s, which I believe is a gcc installation bug. For
SunPRO, the extension modules also build fine).
So before anything is fixed, I'd like to see an actual, reliable,
reproducable error report. The subject of this report (Python 2.5
64 bit compile fails on Solaris 10 with gcc) is not reproducable,
so I'm tempted to close this report as "works for me".
_______________________________________
Python tracker <a class="moz-txt-link-rfc2396E" href="mailto:[EMAIL
PROTECTED]"><[EMAIL PROTECTED]></a>
<a class="moz-txt-link-rfc2396E"
href="http://bugs.python.org/issue1628484";><http://bugs.python.org/issue1628484></a>
_______________________________________
</pre>
</blockquote>
<br>
<div class="moz-signature"><br>
<p>Â </p>
</div>
</body>
</html>
<<attachment: DigiLink_esig_logo.jpg>>
_______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
