Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD 14.0-CURRENT
#7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with the
linker error shown below.
Due to this error, no FreeBSD pkg base nor NanoBSD Image can be build.
[...]
cc -O2 -pipe -O3 -fno-common
-I/po
On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote:
> Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD 14.0-CURRENT
> #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with
> the
> linker error shown below.
>
> Due to this error, no FreeBSD pkg base
On 12/3/21 4:58 AM, Miroslav Lachman wrote:
So beside the update of documentation I really would like to see some
changes to etcupdate workflow where files are modified in temporary
location and moved to destination only if they do not contain any syntax
breaking changes like , , .
On 12/3/21 6:09 PM, Tomoaki AOKI wrote:
On Fri, 03 Dec 2021 05:54:37 -0800 (PST)
"Jeffrey Bouquet" wrote:
On Fri, 3 Dec 2021 13:58:39 +0100, Miroslav Lachman <000.f...@quip.cz> wrote:
On 03/12/2021 12:52, Yetoo Happy wrote:
[...]
Quick Start* and follow the instructions and get to ste
Am 08.12.21 um 18:11 schrieb John Baldwin:
> So the new changes always build a temporary tree (vs trying to build
> /var/db/etupdate/current in place). For -n it should be that it just
> doesn't change /var/db/etcupdate/current at the end, but if it did the
> move anyway that would explain the bug
If it was in a temporary directory, even if I manaually resolved the file
and merge, I was expecting that file marked as resolve to stay in that
temporary directory until I was done with all my files. Maybe I'm confusing
mergemaster -Ui behavior with something else, but it seems like only
merging a
On Wed, 8 Dec 2021 09:11:05 -0800
John Baldwin wrote:
> On 12/3/21 6:09 PM, Tomoaki AOKI wrote:
> > On Fri, 03 Dec 2021 05:54:37 -0800 (PST)
> > "Jeffrey Bouquet" wrote:
> >
> >>
> >>
> >> On Fri, 3 Dec 2021 13:58:39 +0100, Miroslav Lachman <000.f...@quip.cz>
> >> wrote:
> >>
> >>> On 03/12/20
W dniu 3.12.2021 o 14:54, Jeffrey Bouquet pisze:
On Fri, 3 Dec 2021 13:58:39 +0100, Miroslav Lachman <000.f...@quip.cz> wrote:
On 03/12/2021 12:52, Yetoo Happy wrote:
[...]
Thank you Yetoo for describing your experience, bringing the topic again
and provoking this discussion.
Quick
As of my update to (some line splitting applied):
# uname -apKU
FreeBSD CA72_UFS 14.0-CURRENT FreeBSD 14.0-CURRENT #25
main-n251456-22c4ab6cb015-dirty:
Tue Dec 7 19:38:53 PST 2021
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
arm64 aar
[ Note: w...@freebsd.org is only a guess, based on:
https://lists.freebsd.org/archives/dev-commits-src-main/2021-December/001931.html
]
Attempting to update to:
main-n251456-22c4ab6cb015-dirty: Tue Dec 7 19:38:53 PST 2021
resulted in boot failure (showing some boot -v output):
. . .
mmc0: Pro
Hi Mark,
On Wed, 8 Dec 2021 20:36:20 -0800
Mark Millard via freebsd-current wrote:
> [ Note: w...@freebsd.org is only a guess, based on:
> https://lists.freebsd.org/archives/dev-commits-src-main/2021-December/001931.html
> ]
>
> Attempting to update to:
>
> main-n251456-22c4ab6cb015-dirty:
On 2021-Dec-09 08:19:30 +0100, Emmanuel Vadot wrote:
>
> Hi Mark,
>
>On Wed, 8 Dec 2021 20:36:20 -0800
>Mark Millard via freebsd-current wrote:
>
>> [ Note: w...@freebsd.org is only a guess, based on:
>> https://lists.freebsd.org/archives/dev-commits-src-main/2021-December/001931.html
>> ]
>>
>
12 matches
Mail list logo
