On Wed, Oct 23, 2013 at 6:52 AM, Ryan Schmidt <[email protected]> wrote: > > On Oct 23, 2013, at 08:48, Xin Xu <[email protected]> wrote: > >> >> On Oct 23, 2013, at 8:48, Ryan Schmidt <[email protected]> wrote: >> >>> >>> On Oct 23, 2013, at 07:27, Rainer Müller wrote: >>>> On 2013-10-23 12:49, Toshiyuki Kamada wrote: >>>>> I managed to symlink /usr/bin/tar to /usr/bin/gnutar as a quick avoiding >>>>> glitch. >>>> >>>> If you install from source–which is the recommended way at the moment >>>> until a disk image is available–you avoid this problem. >>> >>> It is not only the recommended way, it is the only way: the binary >>> installers are for specific OS X versions, and will prevent installation on >>> the wrong OS X version. >>> >>> So I still don’t know how users are managing to get into this situation, >>> unless it’s by upgrading to Mavericks and forgetting to recompile MacPorts >>> afterward like the Migration page says to do. Yeah, that is exactly what I did wrong. >>> >> >> Will make&make install 2.2.0 from source also have this issue? > > ./configure && make && make install should work fine. Sadly it isn't working for me: complaining about missing Tcl configuration. I'll try to figure out what is going on and fix it. > >> Which is the only way I think to install 2.2.0 on Mavericks. > > Building from source is the only way to install any version of MacPorts on > Mavericks because we have not yet provided any binaries because Mavericks was > only just released. > > _______________________________________________ > macports-users mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-users
-- "Those who would give up Essential Liberty to purchase a little Temporary Safety deserve neither Liberty nor Safety." -- Benjamin Franklin _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
