On Mon, Mar 3, 2014 at 7:03 PM, Alejandro Imass wrote:
> On Mon, Mar 3, 2014 at 6:58 PM, Clemens Lang wrote:
>> Hi Alejandro,
>>
[...]
>> Please don't change stuff in /usr/bin - that's Apple-land. Furthermore, this
>> symlink might later be picked up by MacPorts' configure script during its
>
On Mon, Mar 3, 2014 at 7:03 PM, Alejandro Imass wrote:
> Thanks a lot for both your replies. I will follow the upgrade
> procedure then. I was running a pretty well updated version of Xcode
> and OS X and since my Xcode didn't change I figured it was just a
> minor nuance but apparently it's not.
On Mon, Mar 3, 2014 at 6:58 PM, Clemens Lang wrote:
> Hi Alejandro,
>
> I can assure you that is not the case. I'm on Mavericks, don't have
> /usr/bin/gnutar and no gnutar port installed and gdbm builds fine from source
> (even in the sandbox hiding /usr/local and all files gdbm doesn't depend o
Hi Alejandro,
> Path to gnu tar seems hardcoded in make procedure for gdbm so here's
> how I quickly worked around that problem:
I can assure you that is not the case. I'm on Mavericks, don't have
/usr/bin/gnutar and no gnutar port installed and gdbm builds fine from source
(even in the sandbox
On Mon, Mar 3, 2014 at 6:47 PM, Alejandro Imass wrote:
> Path to gnu tar seems hardcoded in make procedure for gdbm so here's
> how I quickly worked around that problem:
>
If you get an error about /usr/bin/gnutar after upgrading, it means you did
not follow the Migration instructions (
http://t
Hi all,
Path to gnu tar seems hardcoded in make procedure for gdbm so here's
how I quickly worked around that problem:
So if you into /usr/bin/gnutar not found whilst upgrading your ports
after Maveriks just install gnu tar from port (sudo port install
gnutar) and then cd /usr/bin and sudo ln -s
