On Mar 24, 2013, at 18:35, Lawrence Velázquez wrote:
Would it indeed be wise to install clang 3.2 or 3.3
You can certainly install any compiler port and use it to build
individual ports. You can do this by setting configure.compiler on the
command line.
sudo port install foo
On Sun, Mar 24, 2013 at 7:45 PM, Lawrence Velázquez lar...@macports.org wrote:
Not only would it waste space, it would prevent you from using our pre-built
binaries for nearly all ports. We only build +universal packages for
dependencies of i386-only ports.
How does one access these
On Mar 25, 2013, at 6:15 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote:
How does one access these binaries? I'd *much* prefer to obtain
binaries than compile from source on my archaic machine.
By default they get used. They're referred to as archives in the internals
(e.g. port
On Mar 25, 2013, at 12:55, Peter Johansson wrote:
On Sun, Mar 24, 2013 at 7:45 PM, Lawrence Velázquez wrote:
Not only would it waste space, it would prevent you from using our pre-built
binaries for nearly all ports. We only build +universal packages for
dependencies of i386-only ports.
On Mar 24, 2013, at 12:53, Peter Johansson wrote:
Greetings all! I am new to this mailing list but not MacPorts. I
have been using it for about six years now, mostly for small command
line apps - wget, sox, things of that nature. Somewhat recently I
started using it for larger tools like
Greetings all! I am new to this mailing list but not MacPorts. I
have been using it for about six years now, mostly for small command
line apps - wget, sox, things of that nature. Somewhat recently I
started using it for larger tools like Wine and gerbv. While I had
some minor problems, I was
Although I have read the page Using the Right Compiler this page
does not actually provide any insight as to which compiler should be
used to build the MacPorts tree, particularly on older systems with
rather outdated system compilers. It seems as if MacPorts prefers
clang, but by default it
On Mar 24, 2013, at 1:53 PM, Peter Johansson rockets4k...@gmail.com wrote:
I am still running Snow Leopard but I upgraded to the latest XCode for
SL, XCode 4.2. This caused a bunch of problems which I eventually
tracked down to a problem with the clang compiler shipped with XCode 4.2
-- it
On Mar 24, 2013, at 2:53 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote:
I noticed in several places it was suggested to make +universal the
default variant on systems running 64-bit kernels, even aside from Wine.
Is this actually a good procedure?
You certainly can always build
