-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/11/2011 18:30, David Wolfskill wrote:
> On Mon, Jul 11, 2011 at 05:49:09PM -0700, Doug Barton wrote:
>> ...
>
>> I know that you already got some advice on dealing with the specific
>> port that failed, but I wanted to add that 'portmaster -R
On Mon, Jul 11, 2011 at 05:49:09PM -0700, Doug Barton wrote:
> ...
> I know that you already got some advice on dealing with the specific
> port that failed, but I wanted to add that 'portmaster -R -r icu' is
> probably what you want to do next. That will avoid rebuilding the ports
> that did buil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/11/2011 06:21, David Wolfskill wrote:
> Per ports/UPDSATING entry 20110711, and since I use portmaster (thanks,
> Doug!),
My pleasure. :)
> I then invoked the above re-build of icu, and attempt to build the
> ports that weren't built in the p
On Mon, Jul 11, 2011 at 10:12:19AM -0500, Scot Hetzel wrote:
> ...
> > Stop in /common/ports/net/avahi-app.
>
> I also ran into this problem this morning. The problem is that the
> build is picking up /usr/local/lib/libavahi-glib.so.1 (from the old
> avahi-app install) instead of the newly rebuil
On Mon, Jul 11, 2011 at 8:21 AM, David Wolfskill wrote:
> The last port that was successful in taht list was abiword-2.8.4_1; the
> one that followed it was avahi-app-0.6.29. The tail end of that attempt
> looked like:
>
> ...
> CC libavahi_gobject_la-ga-service-resolver.lo
> CC libavah
Per ports/UPDSATING entry 20110711, and since I use portmaster (thanks,
Doug!), I issued
portmaster -r icu
which churned for a while, then came up with teh following list of ports
to upgrade or reinstall:
===>>> The following actions will be taken if you choose to proceed:
Upgra
