Am 01.10.2014 um 22:17 schrieb NGie Cooper:
> On Mon, Sep 29, 2014 at 11:13 PM, O. Hartmann
> <ohart...@zedat.fu-berlin.de> wrote:
>> I just made the last update of the ports yesterday (I use portmaster -da
>> performing this
>> task) and obviously or superficially everything went all right.
>> I'm running on the boxes in question most recent CURRENT.
>> On one system, a subsequent start of updating ports starts to freak out when
>> lang/gcc: it loops over and over on some ports already updated, especially
>> devel/binutils, but the port looping on isn't specific and varies.
>> On every CURRENT box I tried this morning to update the ports again, I find
>> frsutrating message (depends on installation, but it seems in principal the
>> same, only
>> the affected ports in dependency chain varies):
> Are you using portmaster? If so, it might be fallout from r272282.
Yup, after defining
setenv PORTSDIR /usr/ports
my problems, described on my mail in this thread from 30th September,
completely went away.
Thanks for this hint. It helps a lot!
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"