It's a migrated machine from 10.10, latest version. Perhaps it would come from this single fact?
Enviado desde mi iPhone El 2015-08-19, a las 13:07, Chris Jones <jon...@hep.phy.cam.ac.uk> escribió: > > >> On 19 Aug 2015, at 5:49 pm, "semaphor...@yahoo.com" <semaphor...@yahoo.com> >> wrote: >> >> It's not just a matter of compiling, but compilation TIME. It takes >> significantly longer than it would on 10.10. On the other hand, my test is >> done on a hardware machine, not a VM one, so I guess it's just another case >> of "it (doesn't) work on my machine. > > Something is indeed up with your machine i would say. Compilation times in my > vm compare very favourable to those in the host machine, running 10.10. > >> >> Enviado desde mi iPhone >> >>> El 2015-08-19, a las 11:53, Dominik Reichardt <domi...@gmail.com> escribió: >>> >>> >>> >>>> Am 19.08.2015 um 17:18 schrieb Chris Jones <jon...@hep.phy.cam.ac.uk>: >>>> >>>> >>>> >>>>>> On 19/08/15 16:13, C.T. wrote: >>>>>> >>>>>> Experience: 10.11 is still in beta, and it shows. With XCode beta, >>>>>> expect HOURS of compilations for a mere update, and many manual >>>>>> operations since MacPorts doesn’t yet recognizes El Capitan >>>> >>>> I disagree on two of the three points. >>>> >>>> Yes, you should expect to compile all ports as there are no binary >>>> archives as of yet. >>>> >>>> However, as long as you have the correct Xcode installed (the latest beta) >>>> and have installed MacPorts from source, it works just as smoothly in a VM >>>> where I am testing it as in the host OSX10.10 machine. >>>> >>>> Yes its beta, but I've not had any significant issues in the limited >>>> playing I have done in the VM ... >>>> >>>> Chris >>> >>> Thanks, >>> yes, I know it is beta - that doesn't put me off very much, I've used >>> previous betas since 10.7, so I know what to expect. Mostly at this stage >>> it was ok. >>> Whether I migrate during the beta and compile everything or later with the >>> finished system, doesn't matter much to me anyway. Since I tend to need >>> +universal or some other variant, I need to compile most ports instead of >>> just getting the binaries. Also I'm not using that many ports, Gimp is the >>> one with the biggest dependencies... >>> >>> So, seems like I'll backup and jump... >>> >>> Thanks again >>> >>> >>> >>>>>> >>>>>>> El 19 ago 2015, a las 4:41, Dominik Reichardt <domi...@gmail.com> >>>>>>> escribió: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I’m itching to switch but often need MacPorts. Do any of you have >>>>>>> experience yet with it *AND* MacPorts? >>>>>>> >>>>>>> In previous switches, I switched by using the development version of >>>>>>> MacPorts and following the migration steps of any major OS X upgrade, >>>>>>> still the way to go? >>>>>>> >>>>>>> >>>>>>> Take care >>>>>>> >>>>>>> Dom >>>>>>> _______________________________________________ >>>>>>> macports-users mailing list >>>>>>> macports-users@lists.macosforge.org >>>>>>> https://lists.macosforge.org/mailman/listinfo/macports-users >>>>> >>>>> _______________________________________________ >>>>> macports-users mailing list >>>>> macports-users@lists.macosforge.org >>>>> https://lists.macosforge.org/mailman/listinfo/macports-users >>>> _______________________________________________ >>>> macports-users mailing list >>>> macports-users@lists.macosforge.org >>>> https://lists.macosforge.org/mailman/listinfo/macports-users >>> _______________________________________________ >>> macports-users mailing list >>> macports-users@lists.macosforge.org >>> https://lists.macosforge.org/mailman/listinfo/macports-users >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> https://lists.macosforge.org/mailman/listinfo/macports-users _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
