On Dec 9, 2011, at 17:04, Chris Jones wrote:
On 9 Dec 2011, at 10:34pm, Bradley Giesbrecht wrote:
If the dependent port/variant combination installs different files you could
check for their existence/non-existence.
I have no idea. Seems rather messy …
It is messy, but it is the only
On Dec 9, 2011, at 17:14, Scott Webster wrote:
On Fri, Dec 9, 2011 at 2:23 PM, Chris Jones wrote:
Is it possible for a port to check if one of its dependencies is installed
with a required variant, and warn if not ?
I ask since the opengl variant of the root port requires mesa to be
On Dec 9, 2011, at 17:33, Mojca Miklavec wrote:
When running ccmake path-to-root-sources I get the following error:
CMake Error at
/opt/local/share/cmake-2.8/Modules/CMakeDetermineFortranCompiler.cmake:31
(MESSAGE):
Could not find compiler set in environment variable FC:
So set the FC
On Sat, Dec 10, 2011 at 12:11 AM, Ryan Schmidt ryandes...@macports.org wrote:
wine (and wine-devel) only builds 32 bit, so if you want to install it
on a normally 64-bit system you need to make sure all the dependencies
are build universal.
MacPorts does so for you automatically, provided all
On Dec 9, 2011, at 19:33, Mojca Miklavec wrote:
But if I understand it right - when using llvm-gcc/g++ there is
probably no chance to find a fortran compiler unless the user
installed some broken third party variant? Is it OK to have llvm-gcc
set as default compiler without any attempt to
On Dec 10, 2011, at 02:19, Scott Webster wrote:
On Sat, Dec 10, 2011 at 12:11 AM, Ryan Schmidt wrote:
wine (and wine-devel) only builds 32 bit, so if you want to install it
on a normally 64-bit system you need to make sure all the dependencies
are build universal.
MacPorts does so for you
On 10/12/2011 03:24, Phillip Koebbe wrote:
I was referring to the bit about the mail going directly to my inbox and
bypassing the filters I have set up. I use Gmail IMAP and have a filter that
reads the from address and applies a particular label to the message, and when
it comes down to
Hi,
Yes, I'm aware of this. The problem is the opengl variant requires glew to be
installed with the x11 variant, which is not the default. For some reason with
the latest root update this is now causing problems..
I'm working on a solution, which is to use a feature of root which is to build
Chris,
Thank You. I will wait for you to submit your solution
Thanks again
--R
On Sat, Dec 10, 2011 at 07:59, Chris Jones jon...@hep.phy.cam.ac.uk wrote:
Hi,
Yes, I'm aware of this. The problem is the opengl variant requires glew to
be installed with the x11 variant, which is not the
Hi,
I'm experimenting with build the root port with macports clang.
Looking at
https://trac.macports.org/wiki/UsingTheRightCompiler
I thought I could just set configure.compiler to macports-clang-3.1,
analogously to how I use macports gcc compilers, but this fails to configure. I
get
I suspect this should be a bug report ...
Lion 7.2 - Macports 2.0.3
Doing sudo port update outdated when Apache2 is one of the installed ports,
results in the Apache2 file: /opt/local/apache2/htdocs/index.html being
overwritten with the sample.
No copy of the original file is maintained.
Update submitted
https://trac.macports.org/ticket/32491
On 10 Dec 2011, at 3:42pm, Rodolfo Aramayo wrote:
Chris,
Thank You. I will wait for you to submit your solution
Thanks again
--R
On Sat, Dec 10, 2011 at 07:59, Chris Jones jon...@hep.phy.cam.ac.uk wrote:
Hi,
Yes, I'm aware
On Dec 10, 2011, at 12:34, William H. Magill wrote:
I suspect this should be a bug report ...
Lion 7.2 - Macports 2.0.3
Doing sudo port update outdated when Apache2 is one of the installed ports,
results in the Apache2 file: /opt/local/apache2/htdocs/index.html being
overwritten with
On Dec 10, 2011, at 12:14, Chris Jones wrote:
I'm experimenting with build the root port with macports clang.
Looking at
https://trac.macports.org/wiki/UsingTheRightCompiler
I thought I could just set configure.compiler to macports-clang-3.1,
analogously to how I use macports gcc
Hi,
The MacPorts clang-2.9, -3.0 and -3.1 ports are very new, newer than MacPorts
2.0.3, so MacPorts 2.0.3 does not contain these values for
configure.compiler. These values were only added to MacPorts trunk in r86719
on November 1; you can build MacPorts from trunk if you want to try
On Sat, Dec 10, 2011 at 12:31 AM, Ryan Schmidt ryandes...@macports.org wrote:
I can't explain that. That shouldn't be possible. wine-devel has a library
dependency on gst-plugins-base which has a library dependency on gnome-vfs
which has a library dependency on gconf which has a library
Hello,
My mac mini supports 64 bit, the default build for macport is 64 bit.
I want to specify to build macport for 32 bit.
the following command doesn't work.
./configure --build_arch=i386
is there a way to do it?
Thanks.
Peter
___
On Dec 10, 2011, at 15:50, Peter wrote:
My mac mini supports 64 bit, the default build for macport is 64 bit.
I want to specify to build macport for 32 bit.
the following command doesn't work.
./configure --build_arch=i386
is there a way to do it?
The MacPorts binaries you get
Hi Ryan,
The MacPorts binaries you get from our web site are universal: they're for
all architectures.
Why does it matter to you what architecture MacPorts itself is? I suspect
what matters is what architecture MacPorts builds your ports for. That's
controlled via the build_arch
On Dec 10, 2011, at 20:31, Peter wrote:
The MacPorts binaries you get from our web site are universal: they're for
all architectures.
Why does it matter to you what architecture MacPorts itself is? I suspect
what matters is what architecture MacPorts builds your ports for. That's
Trying to get Mailman running under Macports so I can test a collaboration
between mailman and WordPress. No nothing much about Mailman. Been using
Macports for quite some time for web development. So do have LAMP running
as well as Python. Mailman was installed without any issues. Just need to
21 matches
Mail list logo
