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 choices to make: - gcc vs. SunPRO - 32-bit vs. 64-bit - GNU make vs. /usr/ccs/bin/make
I picked the combination which was most easy to setup, and is therefore likely to be used by most users (except for those who think 64-bit is somehow "better" than 32-bit, when it is actually the other way 'round - IMO).
Do not think this is a personal attack.
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 setup. 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
The "-L/usr/local/lib" should be "-L/usr/local/lib/64". An example of many.
Is that really the case? I.e. will ncurses automatically install into /usr/local/lib/64 if built with a 64-bit compiler? My installation doesn't even have a /usr/local/lib/64 folder. In any case: this shouldn't need a configure option. Instead, Python can find out itself whether it's a 64-bit build, and make modifications it considers necessary. Regards, Martin