Hello,
I have just created a ticket for openmpi to suport fortran better.
I found that it does not build if mpich2 is installed.
If we do not allow both to install at the same time,
(is there a counterpart of "Conflicts" field of Fink?)
we do not need to put "open" before mpirun mpicc and mpif90
On Dec 28, 2007, at 1:26 AM, Boey Maun Suang wrote:
Hi Juan,
My current idea is to create a base/config/macports_version file
holding
something like 1.6.1, but the selfupdate
logic of reading the latter over base/config/mp_version has to be
thoroughly thought out: 600 (from base/config/mp_v
On Dec 28, 2007, at 13:37, Pierre Queinnec wrote:
Could it be possible to turn off lint warnings for patches that do
not follow the naming convention (patch-*.diff) but are fetched
using patch_sites? What do you think about that?
I would love for that to happen. A ticket has already been f
Hey all,
Could it be possible to turn off lint warnings for patches that do not
follow the naming convention (patch-*.diff) but are fetched using
patch_sites? What do you think about that?
-- Pierre
___
macports-dev mailing list
macports-dev@lists.m
On Dec 28, 2007, at 10:11, Rainer Müller wrote:
Ryan Schmidt wrote:
Why is it again that we need separate dmgs for separate OS
releases at
all? Why don't we just have a single universal dmg, with the PowerPC
part built with the 10.3.9 SDK and the Intel part built with the
10.4u
SDK, and
Ryan Schmidt wrote:
> Rainer, would you prefer for us to distribute 5 different disk images of
> MacPorts then -- Panther PowerPC, Tiger PowerPC, Tiger Intel, Leopard
> PowerPC, Leopard Intel?
A disk image with four architectures will be around four times bigger
than it needs to be... Why should a
On Dec 24, 2007, at 8:13 PM, Ryan Schmidt wrote:
These lines in a portfile are useless now, right?
platform darwin 8 {
configure.compiler gcc-4.0
}
Ever since default compilers were set in MacPorts base, gcc-4.0 is
the default compiler on darwin 8 anyway, so we can remove these
lin
Ryan Schmidt wrote:
> Why is it again that we need separate dmgs for separate OS releases at
> all? Why don't we just have a single universal dmg, with the PowerPC
> part built with the 10.3.9 SDK and the Intel part built with the 10.4u
> SDK, and everyone's happy? Isn't that the whole point of uni
> Why is it again that we need separate dmgs for separate OS releases
> at all? Why don't we just have a single universal dmg, with the
> PowerPC part built with the 10.3.9 SDK and the Intel part built with
> the 10.4u SDK, and everyone's happy? Isn't that the whole point of
> universal binaries an
Revision
32334
Author
[EMAIL PROTECTED]
Date
2007-12-25 13:33:06 -0800 (Tue, 25 Dec 2007)
Log Message
Clarify that Leopard users need to install Xcode 3.0, while Tiger
users need 2.5 (sorry Anders, no direct link to 2.4 off apple's site
:-P).
As long as you are willing to deal with the breaka
10 matches
Mail list logo