On Thu, 28 May 2015, Ryan Schmidt wrote:
No; the MacPorts default build_arch is x86_64 on Yosemite, but the user
can override it by changing build_arch to i386 in macports.conf. In this
case, the user probably didn't meant to do that, he just imported a
pre-Snow Leopard Intel MacPorts
ok. so it works now.
i did 2 things.
first i set the universal to also include x86_64
tried again and no luck
then i went through the entire migration steps and now i'm up and running.
i hadn't installed macports in my last 2 os upgrades so i wasn't thinking i
had to migrate.
but i guess it was
On May 28, 2015, at 2:47 PM, René J.V. Bertin rjvber...@gmail.com wrote:
It should be safe to build ports that do not depend directly on a failed
port, but it seems not impossible that the ABI-changing effect of the update
of an indirect dependency permeates to a direct dependency.
I would
End users probably don't read the man pages to even know these flags exist.
We're left wondering how and why you're even using them.
-p Despite any errors encountered, proceed to process multiple ports
and com-
mands.
-f force mode (ignore state file)
Do
On Thursday May 28 2015 19:54:27 Kurt Pfeifle wrote:
I've seen the upgrade of 200+ packages stopping just because one of the
first five package upgrade fails.
So have I, but I rarely if ever use even -p when I do launch a bunch of
updates. I rather tend to isolate the ones I know will be
On Thu, May 28, 2015 at 7:28 PM, Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
End users probably don't read the man pages to even know these flags
exist.
That's what I already hinted at in my last mail.
We're left wondering how and why you're even using them.
-p Despite
On May 28, 2015, at 1:09 PM, Kurt Pfeifle kurt.pfei...@googlemail.com wrote:
Ok then: which one of the two switches is the unsafe one? I guess the -f? Or
has the combination of the two even more damage potential?
They're both unsafe.
-f does different things depending on the build phase, but
On Wed, May 27, 2015 at 11:54 PM, Lawrence Velázquez lar...@macports.org
wrote:
On May 27, 2015, at 4:37 PM, Kurt Pfeifle kurt.pfei...@googlemail.com
wrote:
[]
girara was updated an hour ago. Please run a selfupdate and try upgrading
again.
Thanks, it works now.
P.S. Unrelated: Stop
On Thursday May 28 2015 13:33:45 Lawrence Velázquez wrote:
On May 28, 2015, at 1:01 PM, René J.V. Bertin rjvber...@gmail.com wrote:
OP is on Yosemite. MacPorts defaults to x86_64 builds on Yosemite.
even if build_arch is set to i386 only, as was the case for him? Isn't that a
bug?
R
On May 28, 2015, at 1:01 PM, René J.V. Bertin rjvber...@gmail.com wrote:
On Thursday May 28 2015 12:42:20 Lawrence Velázquez wrote:
So the OP is trying to build ImageMagick x86_64.
Are there ways to that other than requesting a +universal build of it, or of
another port which has
I'm confused about the purpose of the thread.
The documentation indicates why what you're doing is a bad thing. You should
just run random commands without knowing what they do.
To quote IRC:
things break so often that i decided that the best course of action was to
ignore the breakage
It
On Thursday May 28 2015 00:14:14 Ryan Schmidt wrote:
Instead of trying to add a patch for this to MacPorts, I would rather you work
with the developers of zlib on including the changes into zlib itself
When the Phoronix article was written, this was being discussed on the zlib ML
and that's
On May 28, 2015, at 12:36 AM, Mojca Miklavec wrote:
On Thu, May 28, 2015 at 4:20 AM, Brandon Allbery wrote:
On Wed, May 27, 2015 at 10:10 PM, Gustavo Seabra wrote:
So, there were 4 (!) versions of grace installed! That should be remnants
of old MacPorts installations. I suppose similar
On May 28, 2015, at 3:30 AM, René J.V. Bertin wrote:
On Thursday May 28 2015 00:14:14 Ryan Schmidt wrote:
Instead of trying to add a patch for this to MacPorts, I would rather you
work with the developers of zlib on including the changes into zlib itself
When the Phoronix article was
-Original Message-
From: Ryan Schmidt [mailto:ryandes...@macports.org]
Sent: 26 May 2015 20:33
To: Larry Velázquez
Cc: Steve Holden; MacPorts Users
Subject: Re: Backing up MacPorts directories
On May 26, 2015, at 12:11 PM, Lawrence Velázquez wrote:
On May 26, 2015, at 7:11 AM,
On Thursday May 28 2015 04:43:28 Ryan Schmidt wrote:
I'm not comfortable with making MacPorts users involuntary testers for
unofficial code in a fundamental library like zlib.
Not on an obligatory basis, no, not until we can show that there are no
drawbacks to it.
I plan to add a variant to
hey all,
i recently upgraded a late 2008 macbookpro to yosemite. with SSD it seems
to work ok.
when running macports to install software i get the following error
quote
Error: Cannot install ImageMagick for the arch(s) 'x86_64' because
Error: its dependency libtool is only installed for the
On Thursday May 28 2015 09:16:46 ^. .^ wrote:
i recently upgraded a late 2008 macbookpro to yosemite. with SSD it seems
Does it have a 64bit processor?
quote
Error: Cannot install ImageMagick for the arch(s) 'x86_64' because
Error: its dependency libtool is only installed for the arch 'i386'
On Thursday May 28 2015 11:02:08 Lawrence Velázquez wrote:
You may have to edit macports.conf again and set universal_archs x86_64 i386.
Was he doing a universal build? ImageMagick doesn't have +universal as a
default variant, so I don't see why one would need universal_archs if one just
wants
On May 28, 2015, at 9:16 AM, ^. .^ sixmilliondollar...@gmail.com wrote:
when running macports to install software i get the following error
quote
Error: Cannot install ImageMagick for the arch(s) 'x86_64' because
Error: its dependency libtool is only installed for the arch 'i386'
On 2015-05-28 15:16, ^. .^ wrote:
i recently upgraded a late 2008 macbookpro to yosemite. with SSD it
seems to work ok.
Did you follow the migration procedure?
http://trac.macports.org/wiki/Migration
when running macports to install software i get the following error
quote
Error: Cannot
On May 28, 2015, at 11:22 AM, René J.V. Bertin rjvber...@gmail.com wrote:
Was he doing a universal build? ImageMagick doesn't have +universal as a
default variant, so I don't see why one would need universal_archs if one
just wants or needs to build the entire tree in 32bit mode ...
On Thursday May 28 2015 12:42:20 Lawrence Velázquez wrote:
So the OP is trying to build ImageMagick x86_64.
Are there ways to that other than requesting a +universal build of it, or of
another port which has ImageMagick as its first dependency?
I must have assumed that the OP would have found
23 matches
Mail list logo
