Hi everyone,
My boss asked me to install MacPorts on a new iMac that arrived to our
office last week, and it shipped with Mac OS X Lion 10.7.3 (so we probably
can't run Snow Leopard on it). I've downloaded MacPorts 2.0.4 but I'm
wondering if I should install it using a slightly older version of
[Tabitha McNerney tabith...@gmail.com (2012-03-17 09:56:56 UTC)]
I've downloaded MacPorts 2.0.4 but I'm
wondering if I should install it using a slightly older version of Xcode
for Lion (like 4.2.1) or if its generally ok and recommended to use
MacPorts 2.0.4 with Xcode 4.3.1 (which is the
Le 16.03.12 17:45, Lawrence Velázquez a écrit :
Hello,
Sorry It desen't work but all is up to date exept amarok witch I can't
install amarok @2.4.3 because libplist 1.8 donpt compile.
Her's below my consol output.
/sudo port install amarok @2.4.3
--- Computing dependencies for amarok
---
On Sat, Mar 17, 2012 at 09:02, Michael Parchet mparc...@sunrise.ch wrote:
*Error: Target org.macports.build returned: shell command failed (see log
for details)
Error: Failed to install libplist
Log for libplist is at:
On Mar 17, 2012, at 10:03 a.m., Brandon Allbery wrote:
On Sat, Mar 17, 2012 at 09:02, Michael Parchet mparc...@sunrise.ch wrote:
Error: Target org.macports.build returned: shell command failed (see log for
details)
Error: Failed to install libplist
Log for libplist is at:
Le 17.03.12 15:03, Brandon Allbery a écrit :
On Sat, Mar 17, 2012 at 09:02, Michael Parchet mparc...@sunrise.ch
mailto:mparc...@sunrise.ch wrote:
/Error: Target org.macports.build returned: shell command failed
(see log for details)
Error: Failed to install libplist
Log for
Le 17.03.12 17:25, Lawrence Velázquez a écrit :
On Mar 17, 2012, at 10:03 a.m., Brandon Allbery wrote:
On Sat, Mar 17, 2012 at 09:02, Michael Parchet mparc...@sunrise.ch
mailto:mparc...@sunrise.ch wrote:
/Error: Target org.macports.build returned: shell command failed
(see log for
On Sat, Mar 17, 2012 at 5:59 AM, Harald Hanche-Olsen han...@math.ntnu.nowrote:
[Tabitha McNerney tabith...@gmail.com (2012-03-17 09:56:56 UTC)]
I've downloaded MacPorts 2.0.4 but I'm
wondering if I should install it using a slightly older version of Xcode
for Lion (like 4.2.1) or if its
On 17 mar 2012, at 18:46, Lawrence Velázquez wrote:
On Mar 17, 2012, at 1:04 p.m., Michael Parchet wrote:
Excuse me I wanted to reopen this ticket because my problem is not yet solve.
What I can do now ?
I have the same problem building libplist on 10.7.3 with Xcode 4.3.1 (4E1019).
As
On Mar 17, 2012, at 2:20 p.m., Daniel Ericsson wrote:
As described in ticket #33431, libplist will build if you manually switch
from clang to the llvm gcc front-end:
sudo port install libplist configure.compiler=llvm-gcc-4.2
Hm, for some reason I thought I was missing llvm-gcc. I'm not
On 2012-03-17 22:38 , Sarma Tangirala wrote:
I was using macports with upgrade and realize it had started to install
all of the available ports.
What was the exact command you were running?
I stopped the process and I was wondering
what is the best way to uninstall these unwanted ports.
Please reply to the list, not only to me.
http://trac.macports.org/wiki/MailingLists#reply
On 2012-03-18 00:29 , Sarma Tangirala wrote:
On 18 March 2012 04:33, Rainer Müller rai...@macports.org
mailto:rai...@macports.org wrote:
On 2012-03-17 22:38 , Sarma Tangirala wrote:
I was
On Mar 17, 2012, at 04:56, Tabitha McNerney wrote:
My boss asked me to install MacPorts on a new iMac that arrived to our office
last week, and it shipped with Mac OS X Lion 10.7.3 (so we probably can't run
Snow Leopard on it). I've downloaded MacPorts 2.0.4 but I'm wondering if I
should
FYI…
I just tried a clean install from scratch using the hack on gcc-4.2
mentioned in that bug #33624. No, intltool still does not build, and is
failing with the same error. So I don't know how that guy (jhkoivis) was
able to build intltool with that hack, when it never gets past the
configure
I have landed in a bit of a funk. Two tales, one solved (but puzzling) and the
other unsolved --
1. On computer A I upgraded Postgres server from 9.0.x to 9.1.3, and Postgis
1.5.3. This caused Geos to be upgraded from 3.3.0 to 3.3.1, but caused gdal
1.8.0 to break. I fixed this by upgrading
1. On computer A I upgraded Postgres server from 9.0.x to 9.1.3, and
Postgis 1.5.3. This caused Geos to be upgraded from 3.3.0 to 3.3.1, but
caused gdal 1.8.0 to break. I fixed this by upgrading gdal 1.8.0 to gdal
1.9.0, but am wondering, why didn't gdal also upgrade when Geos was updated?
On Mar 17, 2012, at 10:58 PM, Jeremy Lavergne wrote:
In any case, I decided to update it all to the latest MacPorts version, and
have now hit a snag with the following message on doing `sudo port install
git-core`
Error: Dependency 'p5.12-error' not found.
Error: Status 1
However, my original error, one that prompted all this dance, still persists.
On my computer A when I do `git push computer_b I get
OpenSSL version mismatch. Built against 105f, you have 1000100f
fatal: The remote end hung up unexpectedly
On computer B I have the right
On Mar 17, 2012, at 11:07 PM, Jeremy Lavergne wrote:
However, my original error, one that prompted all this dance, still
persists. On my computer A when I do `git push computer_b I get
OpenSSL version mismatch. Built against 105f, you have 1000100f
fatal: The remote end hung
Well, I am not sure if it is the issue. On both computers I have the
identical versions of openssl now. See below
computer A$port installed openssl
The following ports are currently installed:
openssl @1.0.0e_0
openssl @1.0.0e_1
openssl @1.0.0g_0
On Mar 17, 2012, at 11:14 PM, Jeremy Lavergne wrote:
Well, I am not sure if it is the issue. On both computers I have the
identical versions of openssl now. See below
computer A$port installed openssl
The following ports are currently installed:
openssl @1.0.0e_0
I get the same error about OpenSSL mismatch. Looking at the date,
/opt/local/bin/ssh-keygen is from Sep 11, 2011. Do I need to update that? If
yes, what port is that a part of, since I can't find it standalone on
macports.
You can run `port provides FILE` to find out which package a give
On Mar 17, 2012, at 11:27 PM, Jeremy Lavergne wrote:
I get the same error about OpenSSL mismatch. Looking at the date,
/opt/local/bin/ssh-keygen is from Sep 11, 2011. Do I need to update that? If
yes, what port is that a part of, since I can't find it standalone on
macports.
You can
You can use the force switch to make it uninstall and then reinstall
it. Or, as Jeremy suggested earlier, perhaps sudo port upgrade
--force openssl will force it to rebuild.
Scott
On Sat, Mar 17, 2012 at 9:34 PM, Mr. Puneet Kishor punk.k...@gmail.com wrote:
On Mar 17, 2012, at 11:27 PM,
Sadly, I can't just uninstall openssl and reinstall it. A million other ports
depend on it, and it won't let me uninstall it. Just doing a port install
doesn't help. I am caught in some kind of a nasty loop here.
Suggestions?
sudo port -f uninstall openssl
sudo port install openssl.
On Mar 17, 2012, at 23:12, Mr. Puneet Kishor wrote:
Yet, on computer A, I get the following error
computer A$git push computer_B
OpenSSL version mismatch. Built against 105f, you have 1000100f
fatal: The remote end hung up unexpectedly
what is it trying to tell me?
On Mar 17, 2012, at 19:44, Jeff Singleton wrote:
I just tried a clean install from scratch using the hack on gcc-4.2 mentioned
in that bug #33624.
You mean #33264. I certainly cannot advocate that gcc hack; that's completely
not how we handle archs in MacPorts.
No, intltool still does not
27 matches
Mail list logo
