On 2/25/07, Timothy Lyons <[EMAIL PROTECTED]> wrote:
>
> On 24 Feb 2007, at 03:12, Alexander Hansen wrote:
>
> > On 2/23/07, Tim Lyons <[EMAIL PROTECTED]> wrote:
> >> Could someone please tell me which packages hold:
> >>
> >> (1) the python bindings for GNOME print
> >> (2) the python bindings for
Considering that Apple will likely be announcing dual quad core
systems in the near future, I wonder if fink should adopt some
policy on packaging that utilizes the extra cores. Specifically
if we should have two changes. One would be a setting in fink.conf
which would either allow fink to use a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Howarth wrote:
>Considering that Apple will likely be announcing dual quad core
> systems in the near future, I wonder if fink should adopt some
> policy on packaging that utilizes the extra cores. Specifically
> if we should have two changes.
>Considering that Apple will likely be announcing dual quad core
> systems in the near future, I wonder if fink should adopt some policy
> on packaging that utilizes the extra cores. Specifically if we should
> have two changes. One would be a setting in fink.conf which would
> either allow fin
Matt Stephenson's raster3d package currently depends on gcc4 but
breaks when compiled with gcc42.
Jack Howarth fixed it so that it now compiles with the latter.
Would it be ok if I updated this package in cvs?
Bill
-
David,
What I am suggesting is not quite making the packages
build as multi-procs by default by rather allow certain
very large packages (like gcc42) do so if the user
consents. Also, I'm not suggesting injecting MAKEFLAGS
into the user environment. What I was suggesting that
the user have veto
I've been doing this:
eg (from cctbx):
# Find the number of cpus:
num_cpu=$( sysctl hw.logicalcpu | awk '{print $NF}' )
# On a machine with multiple CPUs enter:
libtbx.scons -j $num_cpu .
So far no one has complained, so I am hoping it is legal...
(It doesn't ask permission.)
Bill
-
On Feb 25, 2007, at 10:19 AM, William Scott wrote:
> Matt Stephenson's raster3d package currently depends on gcc4 but
> breaks when compiled with gcc42.
>
> Jack Howarth fixed it so that it now compiles with the latter.
>
> Would it be ok if I updated this package in cvs?
>
> Bill
Yes, I think i
Are there any plans to make a pyqt version with intel compatibility
available?
--
Package manager version: 0.26.1
Distribution version: 0.8.1.rsync i386
Mac OS X version: 10.4.8
Xcode version: 2.4.1
gcc version: 4.0.1 (Apple Computer, Inc. build 5367)
make version: 3.80
Feedback Courtesy of Fink