careless commits disrupt

[Cy Schubert]

Yes, failure to delete old files can also lead to weird ports build failures.

---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.

Cy Schubert
<Cy.Schubert at cschubert.com> or <cy at freebsd.org>
The need of the many outweighs the greed of the few.
---

-----Original Message-----
From: Stefan Esser
Sent: 11/10/2018 11:42
To: Julian H. Stacey
Cc: FreeBSD Current
Subject: Re: careless commits disrupt

Am 11.10.18 um 18:20 schrieb Julian H. Stacey:
>> On Thu, Oct 11, 2018 at 05:54:08PM +0200, Julian H. Stacey wrote:
>>> ....
>>> 3_sxnet.pico v3_tlsf.pico v3_utl.pico v3err.pico |  tsort -q`  -lpthread
>>> /usr/bin/ld: error: unable to find library -lpthread
>>> cc: error: linker command failed with exit code 1 (use -v to see invocati=
>> on)
>>> *** Error code 1
>>> =20
>>> Stop.
>>> make[4]: stopped in /usr/src/secure/lib/libcrypto
>>> =20
>>> Yes I'm current:
>>> 	.ctm_status src-cur 13733
>>> 	.svn_revision 339303
>>> ....
>>
>> I had no issues this morning performing a src-based update from
>> head/amd64 @r339278 to r339303 -- either on my laptop or my build
>> machine.
> 
> Hi David, 
> Then it seems this one is hopefuly my local problem then,
> so I'll revert to vanilla r339303 & retry. Thanks.

It worked for me when I started with a clean /usr/obj.

You should also delete old files:

cd /usr/src
make delete-old
make delete-old-libs

Regards, STefan
_______________________________________________
freebsd-current at freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"