Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-12 Thread Gary Jennejohn
On Thu, 12 Jan 2023 10:37:34 -0700 Warner Losh wrote: > On Thu, Jan 12, 2023 at 4:44 AM David Wolfskill > wrote: > > > > I had this problem also. After deleting obj/usr the buildworld > succeeded. > > > > > > > > > > > > > Empirically: > > rm -fr /usr/obj/usr/src/amd64.amd64/u

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-12 Thread Warner Losh
On Thu, Jan 12, 2023 at 4:44 AM David Wolfskill wrote: > On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > > looks like we may need another 'unclean' workaround for this? > > > > Warner > > > > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > > ... > > > I had this problem al

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-12 Thread Gary Jennejohn
On Fri, 13 Jan 2023 01:31:59 +0900 Tomoaki AOKI wrote: > On Thu, 12 Jan 2023 14:41:19 + > Gary Jennejohn wrote: > [SNIP] > > > > I installed the new world on my tower this morning. Now I see a new > > problem. > > > > I don't know whether this new problem is related to the new tzcode, but >

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-12 Thread Tomoaki AOKI
On Thu, 12 Jan 2023 14:41:19 + Gary Jennejohn wrote: > On Thu, 12 Jan 2023 03:44:03 -0800 > David Wolfskill wrote: > > > On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > > > looks like we may need another 'unclean' workaround for this? > > > > > > Warner > > > > > > On Wed, Ja

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-12 Thread Gary Jennejohn
On Thu, 12 Jan 2023 03:44:03 -0800 David Wolfskill wrote: > On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > > looks like we may need another 'unclean' workaround for this? > > > > Warner > > > > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > > ... > > > I had this problem

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-12 Thread David Wolfskill
On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote: > looks like we may need another 'unclean' workaround for this? > > Warner > > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > ... > > I had this problem also. After deleting obj/usr the buildworld succeeded. > > > Empi

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-11 Thread Warner Losh
looks like we may need another 'unclean' workaround for this? Warner On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote: > On Wed, 11 Jan 2023 04:05:43 -0800 > David Wolfskill wrote: > > > Running: > > FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275 > main-n259988-48d

Re: Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-11 Thread Gary Jennejohn
On Wed, 11 Jan 2023 04:05:43 -0800 David Wolfskill wrote: > Running: > FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275 > main-n259988-48dc9150ac36: Tue Jan 10 12:20:47 UTC 2023 > r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC > amd64 >

Build failure: main-n259988-48dc9150ac36 -> main-n260011-40bb52c89b87

2023-01-11 Thread David Wolfskill
Running: FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275 main-n259988-48dc9150ac36: Tue Jan 10 12:20:47 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 and performing an in-place source update to main-n260011-40bb52c89b87 u