On Wed, 27 Sep 2006 12:17:29 -0700, Doug Barton <[EMAIL PROTECTED]> wrote:
> Bill Blue wrote:
>
>> Ok, I have found the problem. I had mis-specified the port group
>> that a particular port was in. xmixer is in audio, not x11, for
>> example.
>>
>> if you use portmaster's -p option to specify th
Bill Blue wrote:
> Ok, I have found the problem. I had mis-specified the port group
> that a particular port was in. xmixer is in audio, not x11, for
> example.
>
> if you use portmaster's -p option to specify the path to a port and
> that path doesn't exist, portmaster will display a message t
On Wed, 20 Sep 2006 14:49:05 -0700, Bill Blue <[EMAIL PROTECTED]> wrote:
> I have updated and rebuilt the entire installed ports tree, but afterwards
> when trying to add/build xmixer, ruby18-shout and a few others, I'm still
> getting the same failures in accessibility/dasher (as described earl
I have updated and rebuilt the entire installed ports tree, but afterwards when
trying to add/build xmixer, ruby18-shout and a few others, I'm still getting
the same failures in accessibility/dasher (as described earlier) even though
dasher itself will build with no problems.
Additionally, when
