On Apr 6, 2020, at 06:49, Dave Horsfall wrote:
> Was just communing with nature, and I see that "clang" finally got built;
> it's now hammering on "gnutls" so I may as well go back to bed and pick up
> the debris in the morning...
I did put in an update of wine yesterday, so we now have
Was just communing with nature, and I see that "clang" finally got built;
it's now hammering on "gnutls" so I may as well go back to bed and pick up
the debris in the morning...
-- Dave
On Apr 6, 2020, at 03:39, Christopher Jones wrote:
> On 6 Apr 2020, at 8:42 am, Dave Horsfall wrote:
>
>> On Mon, 6 Apr 2020, Ryan Schmidt wrote:
>>
>>> You should not routinely use the -p flag like this.
>>
>> I did that following advice on this list about a year ago, when some port
>>
> On 6 Apr 2020, at 8:42 am, Dave Horsfall wrote:
>
> On Mon, 6 Apr 2020, Ryan Schmidt wrote:
>
>> You should not routinely use the -p flag like this.
>
> I did that following advice on this list about a year ago, when some port
> ("guile"?) that I'd never even heard of would not build.
>
On Mon, 6 Apr 2020, Ryan Schmidt wrote:
You should not routinely use the -p flag like this.
I did that following advice on this list about a year ago, when some port
("guile"?) that I'd never even heard of would not build.
Do you mean openssl? or libressl? or something else?
On Apr 6, 2020, at 00:21, Dave Horsfall wrote:
> So this morning I do my weekly "port selfupdate" and "port upgrade -p
> outdated" (I use "-p" to make it keep going with the rest of the ports, come
> hell or high water),
You should not routinely use the -p flag like this.
> and after
So this morning I do my weekly "port selfupdate" and "port upgrade -p
outdated" (I use "-p" to make it keep going with the rest of the ports,
come hell or high water), and after updating SSL it's now rebuilding what
appears to be the rest of the world (cmake, llvm, clang, assorted other
ports
