On Mon, Sep 12, 2011 at 5:33 PM, Ryan Schmidt wrote:
> On Sep 12, 2011, at 14:52, William H. Magill wrote:
>
>> Note: this particular error happened before I realized I did not upgrade
>> Xcode on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed
>> again after updating to Xcode
On Sep 12, 2011, at 14:54, William H. Magill wrote:
> ==
> # 27 inch iMac Intel (mid 2010) - 27 inch diagonal screen - Acquired 6/2011
> Model
> Processor 2.93 GHz Intel Core i7
> Memory 4 GB 1333 MHz DDR3
> Graphics ATI Radeon
On Sep 12, 2011, at 14:52, William H. Magill wrote:
> Note: this particular error happened before I realized I did not upgrade
> Xcode on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed
> again after updating to Xcode 4.1.)
> This posting is simply "for the record" -- that the
On Sep 12, 2011, at 15:13, Alexander Skwar wrote:
> Don't know if it matters, but I had several old versions still
> registered:
>
> MacBook-Pro:local alex$ sudo port -f uninstall libiconv
> ---> The following versions of libiconv are currently installed:
> ---> libiconv @1.13.1_0
> --->
Hi,
I should add the variant worked fine until recently, around the time Lion was
released. I'm testing it on Lion myself.
Chris
On 12 Sep 2011, at 9:32pm, Chris Jones wrote:
> Hi,
>
> I am trying to fix a problem with the root port and the python26 variant. The
> code for the variant is bel
Hi,
I am trying to fix a problem with the root port and the python26 variant. The
code for the variant is below.
As far as I can tell, the configure step for the build fails because the
python-libdir directory does not have a lib libpython.dylib file. It only has
the versioned file libpython2.
Hello again.
On Mon, Sep 12, 2011 at 10:32, Ryan Schmidt wrote:
>
> On Sep 11, 2011, at 15:37, Alexander Skwar wrote:
>
>> Earlier today, I wanted to upgrade from Macports 1.9.2 to
>> 2.0.3 on my OSX 10.6.8 system. Well, it didn't work out…
>>
>> http://pastebin.com/he85hMaP
>
> The curious error
Good evening,
On Mon, Sep 12, 2011 at 10:37, Ryan Schmidt wrote:
> On Sep 12, 2011, at 03:32, Ryan Schmidt wrote:
>
>> I wonder if MacPorts is trying to use MacPorts' own bzip2 to decompress the
>> archive; if so, that of course won't work, as you noted below.
>>
>>> As you can see there (or als
Note: this particular error happened before I realized I did not upgrade Xcode
on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed again
after updating to Xcode 4.1.)
This posting is simply "for the record" -- that the message needs to be
expanded :).
outpost> sudo port selfupd
On Sep 12, 2011, at 03:32, Ryan Schmidt wrote:
> I wonder if MacPorts is trying to use MacPorts' own bzip2 to decompress the
> archive; if so, that of course won't work, as you noted below.
>
>> As you can see there (or also further down), an update failed.
>> Also when I try to start bzip2 or (
On Sep 11, 2011, at 15:37, Alexander Skwar wrote:
> Earlier today, I wanted to upgrade from Macports 1.9.2 to
> 2.0.3 on my OSX 10.6.8 system. Well, it didn't work out…
>
> http://pastebin.com/he85hMaP
The curious error here is:
Error: Target org.macports.activate returned: Image error: Source
11 matches
Mail list logo
