-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 13:19, Jesus Cea wrote:
> Would be acceptable to change something like:
>
> """
> add_library_path("/usr/local/lib")
> """
>
> to something similar to:
>
> """
> if (platform.uname()=="SunOS") and (platform.architecture()[0]=="64bits") :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 07:55, "Martin v. Löwis" wrote:
>> >> But if we say the Python can be compiled as 64 bits under Solaris,
would
>> >> be nice if that was actually true. Now that we have a buildbot (under
>> >> OpenIndiana) to test, it is doable.
> >
> > But
> But if we say the Python can be compiled as 64 bits under Solaris, would
> be nice if that was actually true. Now that we have a buildbot (under
> OpenIndiana) to test, it is doable.
But it is true, and always has been true. The lib/64 issue did not
prevent one building Python on Solaris/SPARC64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 01:05, "Martin v. Löwis" wrote:
> I just point out that none of the binaries in /usr/bin is a 64-bit
> binary; this includes the Sun-provided /usr/sfw/bin/python
True. This is for simplicity reasons (provide only one binary valid for
32 an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/11/10 01:05, "Martin v. Löwis" wrote:
> No offense taken. If you really want to know the historical background:
> this was the very first build slave (before I actually announced it to
> python-dev), and I haven't changed much from the initial se
Am 23.11.2010 00:48, schrieb Jesus Cea:
> I think this is probably trivial, but is there any foolproof way to
> detect 64 bit builds in python, beside "sys.maxint"?.
The canonical way is to use platform.architecture().
> And any macro useable for conditional compilation in C?.
You need to be mor
On Mon, Nov 22, 2010 at 17:48, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think this is probably trivial, but is there any foolproof way to
> detect 64 bit builds in python, beside "sys.maxint"?.
>
import platform
platform.architecture()
On Tue, 23 Nov 2010 00:48:06 +0100
Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I think this is probably trivial, but is there any foolproof way to
> detect 64 bit builds in python, beside "sys.maxint"?.
sys.maxsize
> And any macro useable for conditional compilation i
Am 23.11.2010 00:41, schrieb Jesus Cea:
> On 22/11/10 23:05, "Martin v. Löwis" wrote:
>>> PS: Martin, is there any reason to restrict the solaris 10 buildslaves
>>> to 32 bits, beside the said problems?.
>
>> I don't see that as a restriction. I have to make a choice, and there
>> are sooo many ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think this is probably trivial, but is there any foolproof way to
detect 64 bit builds in python, beside "sys.maxint"?.
And any macro useable for conditional compilation in C?.
Checking Solaris 10 header files, I see macros like "_LP64". Portabilit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/10 23:05, "Martin v. Löwis" wrote:
>> PS: Martin, is there any reason to restrict the solaris 10 buildslaves
>> to 32 bits, beside the said problems?.
>
> I don't see that as a restriction. I have to make a choice, and there
> are sooo many c
Am 22.11.2010 23:51, schrieb Éric Araujo:
> Hi,
>
> I think this bug is related: http://bugs.python.org/issue1294959
> “Problems with /usr/lib64 builds.”
Perhaps more closely related:
http://bugs.python.org/issue847812
http://bugs.python.org/issue1733484
http://bugs.python.org/issue1676121
http:
Hi,
I think this bug is related: http://bugs.python.org/issue1294959
“Problems with /usr/lib64 builds.”
Regards
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/ma
In article <4ceae129.2060...@jcea.es>, Jesus Cea wrote:
> On 22/11/10 20:42, "Martin v. Löwis" wrote:
> > Before enabling anything on a build slave, a patch needs to be
> > contributed to make it work in the first place.
>
> I actually agree. I am not sure yet, but I am thinking that adding a
> "
> I actually agree. I am not sure yet, but I am thinking that adding a
> "--build-64" parameter to "configure" could be an option under Solaris.
> Most OSs (let say, Linux) force you to choose 32/64 bits at install
> time
Actually, that's not at all the case. Most systems these days support
32-bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/10 20:42, "Martin v. Löwis" wrote:
> Before enabling anything on a build slave, a patch needs to be
> contributed to make it work in the first place.
I actually agree. I am not sure yet, but I am thinking that adding a
"--build-64" parameter
> Solaris overcomes most of the issue having separate library searchpath
> in 32 and 64 bits (via the "crle" command). But in some cases python try
> to find some library in "/usr/local/lib", and my point is that it should
> search TOO inside "/usr/local/lib/64".
I don't think this will work. If t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/10 20:12, Brett Cannon wrote:
> Are you asking about buildbots only or as a general policy? If you are
> asking about the buildbots then I definitely think we should use 64
> bits. If you are asking about policy I would say it should be an
> o
On Mon, Nov 22, 2010 at 10:34, Jesus Cea wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> A Solaris installation contains ALWAYS 32 and 64 bits libraries. So in
> any Solaris you can run 32/64 bits programs, and compile in 32 and 64 bits.
>
> For this, libraries are stores in "/usr/lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A Solaris installation contains ALWAYS 32 and 64 bits libraries. So in
any Solaris you can run 32/64 bits programs, and compile in 32 and 64 bits.
For this, libraries are stores in "/usr/lib", for instance, for 32 bits,
while the same 64 bits librarie
20 matches
Mail list logo
