On 2010-6-17 02:24 , Adam Mercer wrote:
Hi
There are several tickets open regarding build issues that can
essentially be stemmed to the problem that the NumPy and SciPy, at the
moment, do not support universal variants. The first of which #19397
[1] provides a solution to the universal
Le 17 juin 2010 à 17:48, Joshua Root a écrit :
I don't know why anyone would need a universal scipy or numpy. Do they
have any dependents that only build for a particular arch? It might be
best to just mark all the dependents as non-universal too.
Well, that's not a question especially tied
On Thu, Jun 17, 2010 at 9:34 AM, vincent habchi vi...@macports.org wrote:
Well, that's not a question especially tied to scipy or numpy. Question is:
with the rapid obsolescence of ppc* and i386 machines, what's the point in
compiling universal apps ? If the response is: compile on a fast
On 2010-6-18 04:30 , Scott Webster wrote:
On Thu, Jun 17, 2010 at 9:34 AM, vincent habchi vi...@macports.org wrote:
Well, that's not a question especially tied to scipy or numpy. Question is:
with the rapid obsolescence of ppc* and i386 machines, what's the point in
compiling universal apps
On Thu, Jun 17, 2010 at 10:48, Joshua Root j...@macports.org wrote:
I don't know why anyone would need a universal scipy or numpy. Do they
have any dependents that only build for a particular arch? It might be
best to just mark all the dependents as non-universal too.
I agree, but I think one
On 2010-6-18 05:12 , Adam Mercer wrote:
On Thu, Jun 17, 2010 at 10:48, Joshua Root j...@macports.org wrote:
I don't know why anyone would need a universal scipy or numpy. Do they
have any dependents that only build for a particular arch? It might be
best to just mark all the dependents as
Le 17 juin 2010 à 20:30, Scott Webster a écrit :
On Thu, Jun 17, 2010 at 9:34 AM, vincent habchi vi...@macports.org wrote:
Well, that's not a question especially tied to scipy or numpy. Question is:
with the rapid obsolescence of ppc* and i386 machines, what's the point in
compiling
On Thu, Jun 17, 2010 at 02:12:08PM -0500, Adam Mercer said:
On Thu, Jun 17, 2010 at 10:48, Joshua Root j...@macports.org wrote:
I don't know why anyone would need a universal scipy or numpy. Do they
have any dependents that only build for a particular arch? It might be
best to just mark
On Thu, Jun 17, 2010 at 14:24, Joshua Root j...@macports.org wrote:
I agree, but I think one problem is that NumPy uses the same compiler
flags as were used to build Python (at least that used to be the
case), so if Python was built universally so was NumPy - not sure if
this is still the
On Jun 17, 2010, at 14:32, vincent habchi wrote:
I think we ought to identify these apps and figure out why they are 32-bit
only and if they could be upgraded. AFAIK, 32-bit only was tied to the GUI
using Carbon instead of Cocoa.
Yes, a lot of the ports that are 32-bit-only are because of
Ryan,
Yes, a lot of the ports that are 32-bit-only are because of Carbon. wxWidgets
comes to mind. The developers are working on the problem; who knows how long
it will take.
Yes, I know that. I am afraid the wx-cocoa part is lacking help from
experienced Cocoa users. I begin to have a
Adam,
Le 16 juin 2010 à 18:24, Adam Mercer a écrit :
There are several tickets open regarding build issues that can
essentially be stemmed to the problem that the NumPy and SciPy, at the
moment, do not support universal variants. The first of which #19397
[1] provides a solution to the
On Wed, Jun 16, 2010 at 12:09, vincent habchi vi...@macports.org wrote:
Vincent
- Further testing, especially on the new i7 machines: gcc43 seems to be
incompatible, gcc45 seems to work, but gcc44 behavior is unknown to me at
this time;
- Maintainer's approval :)
I believe this i7
Adam
I believe this i7 incompatiblity was the reason for ATLAS to use gcc44
instead of gcc43, but testing is important.
I know that I systematically told the people that experienced bugs with Atlas
on their i7 machine to use the newest possible gcc, that is gcc45, and it
worked. But I am not
14 matches
Mail list logo
