Yosemite upgrade

Sun Oct 19 10:04:52 PDT 2014

> On 19 Oct 2014, at 6:00 pm, Carlo Tambuatco <oraclmaster at gmail.com> wrote:
> 
> I'd like to get some feedback on those logfiles I sent first before I do a clean wipe of all my macports and spend the next 10 hours or so downloading, configuring, building and reinstalling 459 separate ports. There may be a simpler solution.

So do i take it that you didn't do this when you upgraded, i.e. You didn't properly follow the migration guide ? If so, then thats your problem. You need to do what it says, there is no alternative.

> 
>> On Sun, Oct 19, 2014 at 12:57 PM, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>> Hi,
>> 
>>> On 19 Oct 2014, at 5:50 pm, Carlo Tambuatco <oraclmaster at gmail.com> wrote:
>>> 
>>> I upgraded to Xcode 6.1, installed the command line tools for 10.10, re-installed macports using the appropriate 10.10 installer .dmg. Then upgraded all my macports. The only thing I can think of that you may be referring to that I have not done so far is update the macports.conf file...?
>> 
>> When you say you upgraded all your ports, did you do this exactly how the guide says ? I.e. Did you first uninstall them all, then, reinstall them from scratch ?
>> 
>>> 
>>> From the macports migration page:
>>> 
>>> "If your macports.conf contains uncommented settings for universal_archs or build_arch, you will likely want to update them, since unlike earlier OS versions, the compiler on Snow Leopard and later will build for x86_64 by default on systems that support it. The default values will be fine for almost all users, so unless you know you need something different, just comment out these two lines.
>>> 
>>> Several other settings in macports.conf have changed their defaults over the years. Take a moment to compare each line of your macports.conf with the corresponding line in macports.conf.default in the same directory. Unless you know a reason why a line your settings file should be different from the defaults, adopt the line from the defaults file."
>>> 
>>> I don't really know enough about these settings to mess with them myself. Did you change any values in the macports.conf file or macports.conf.default file to get it to work? Other than this I can't think of anything I did that is different to the steps for migrating macports.
>>> 
>> I did not touch any conf files.
>> 
>> I still think something went wrong and some memory of your previous OSX 10.9 installations is still present. I cannot see how you would get messages regarding Darwin 13 otherwise. At this point i would perhaps suggest completely wiping macports
>> 
>> https://guide.macports.org/chunked/installing.macports.uninstalling.html
>> 
>> Then reinstall from scratch.
>> 
>> Chris
>> 
>>> 
>>> 
>>> 
>>>> On Sun, Oct 19, 2014 at 12:34 PM, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>>>> Hi,
>>>> 
>>>> gcc48 and libgcc installed fine for me in a OSX10.10 VM I had running with the Xcode 6.1 beta prelease. Did you correctly follow the MacPorts migration guide after upgrading your OS.
>>>> 
>>>> https://trac.macports.org/wiki/Migration
>>>> 
>>>> The references below to Darwin 13 (OSX 10.9) suggests to me you did not follow the migration instructions..
>>>> 
>>>> Chris
>>>> 
>>>> 
>>>> 
>>>>> On 19 Oct 2014, at 4:15 pm, Carlo Tambuatco <oraclmaster at gmail.com> wrote:
>>>>> 
>>>>> Just upgraded to XCode 6.1. There are still a few hiccups, ports that fail to upgrade for one reason or another:
>>>>> 
>>>>> db46                           4.6.21_9 < 4.6.21_9  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> gcc47                          4.7.4_1 < 4.7.4_1  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> gcc48                          4.8.3_0 < 4.8.3_0  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> libgcc                         4.9.1_0 < 4.9.1_0  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> llvm-3.3                       3.3_4 < 3.3_4  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> py26-wxpython-2.8              2.8.12.1_0 < 2.8.12.1_0  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> pypy                           2.4.0_0 < 2.4.0_0  (platform darwin 13 != darwin 14)  
>>>>> 
>>>>> v8                             3.23.17.23_1 < 3.23.17.23_1  (platform darwin 13 != darwin 14) 
>>>>> 
>>>>> 
>>>>> 
>>>>> The failure of gcc47 and gcc48 seem to be connected to the failure to configure llvm-3.3
>>>>> 
>>>>> Here's the specific llvm-3.3 error:
>>>>> 
>>>>> Error: Failed to configure llvm-3.3, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.3/llvm-3.3/work/llvm-3.3.src/config.log
>>>>> 
>>>>> 
>>>>> Error: org.macports.configure for port llvm-3.3 returned: configure failure: command execution failed
>>>>> 
>>>>> I will attach the log file for the llvm-3.3 error.
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> pypy fails because of a checksum mismatch:
>>>>> 
>>>>> Error: Checksum (md5) mismatch for pypy-2.4.0-src.tar.bz2
>>>>> 
>>>>> Error: Checksum (sha1) mismatch for pypy-2.4.0-src.tar.bz2
>>>>> 
>>>>> Error: Checksum (rmd160) mismatch for pypy-2.4.0-src.tar.bz2
>>>>> 
>>>>> 
>>>>> Error: org.macports.checksum for port pypy returned: Unable to verify file checksums
>>>>> 
>>>>> 
>>>>> 
>>>>> I'm not sure what the problem with v8 is so I'll try to attach the log file for that as well.
>>>>> 
>>>>> 
>>>>>> On Sat, Oct 18, 2014 at 8:16 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
>>>>>> Remember to Reply All when you reply.
>>>>>> 
>>>>>> 
>>>>>> On Oct 18, 2014, at 7:13 PM, Carlo Tambuatco wrote:
>>>>>> 
>>>>>> > Yeah, just upgraded my ports yesterday after upgrading to Yosemite, and cmake along with other ports such as pypy etc fail to upgrade properly. I am using the Xcode 6.0 toolchain, so do I need to wait for Xcode 6.1 to be released officially before upgrading these ports?
>>>>>> 
>>>>>> Yes, to build cmake, you need the 10.10 SDK. It's in Xcode 6.1, both the final version which Apple will release to everyone later and the pre-release versions, if you can still find it, or the beta versions (but not the final version) of Xcode 6.0.
>>>>>> 
>>>>>> 
>>>>>> > Ports that have failed the upgrade process after migrating to Yosemite:
>>>>>> >
>>>>>> > apple-gcc42                    @5666.3         lang/apple-gcc42
>>>>>> 
>>>>>> apple-gcc42 is not supported on Yosemite for now.
>>>>>> 
>>>>>> > clisp                          @2.49           lang/clisp
>>>>>> > cmake                          @3.0.2          devel/cmake
>>>>>> > db46                           @4.6.21         databases/db46
>>>>>> > gcc47                          @4.7.4          lang/gcc47
>>>>>> 
>>>>>> I haven't yet fixed gcc47 and lower for Yosemite, though I intend to. gcc48 and up should work.
>>>>>> 
>>>>>> > gcc48                          @4.8.3          lang/gcc48
>>>>>> > gstreamer1-gst-plugins-base    @1.4.3          gnome/gstreamer1-gst-plugins-base
>>>>>> > libgcc                         @4.9.1          lang/gcc49
>>>>>> > llvm-3.3                       @3.3            lang/llvm-3.3
>>>>>> > llvm-gcc42                     @2336.11        lang/llvm-gcc42
>>>>>> 
>>>>>> llvm-gcc42 is not supported on Yosemite for now.
>>>>>> 
>>>>>> > py26-wxpython-2.8              @2.8.12.1       python/py-wxpython-2.8
>>>>>> > pypy                           @2.4.0          lang/pypy
>>>>>> > v8                             @3.23.17.23     lang/v8
>>>>>> 
>>>>>> 
>>>>> 
>>>>> <logfiles.zip>
>>>>> _______________________________________________
>>>>> macports-users mailing list
>>>>> macports-users at lists.macosforge.org
>>>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>>> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20141019/17a99955/attachment.html>