Re: Thoughts about ports freeze
in message [EMAIL PROTECTED], wrote Sid Carter thusly... On Fri, 20 Dec 2002 07:51:48 +0100, [EMAIL PROTECTED] (Dirk Meyer) said: Dirk I have 29 updates/committs in the queue, waiting for the freeze is over. Dirk No offense, I know the problems, but I think the freeze is way to long. the way it is going, it seems as tho' the freeze is gonna stay till the 2nd quarter of 2003 or something. Just my thougts, no offense meant :) ice age cometh. get thine blankie und hoard the nuts. :-] - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Intel 82574 issue reported on Slashdot
in message a18965a6-8d17-4919-9947-fe43d2503...@gsoft.com.au, wrote Daniel O'Connor thusly... On 09/02/2013, at 4:46, Jack Vogel jfvo...@gmail.com wrote: recommends contacting your motherboard manufacturer if you have continued concerns or questions whether your products are impacted. Here is the link: http://communities.intel.com/community/wired/blog/2013/02/07/intel-82574l-gigabit-ethernet-controller-statement Any questions or concerns may be sent to me. In all honesty.. The blog post (and your email) are basically information free, they don't name names and provide no script or downloadable code that will allow end users to check if they are affected. Contact your motherboard manufacturer is much more time consuming than Run sysctl... | grep foo | awk ... to see if your system is affected. Gift^WStraight from horse's mouth ... http://blog.krisk.org/2013/02/packets-of-death.html http://www.kriskinc.com/intel-pod - parv -- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Could not change brightness anymore with i915kms & acpi_video modules c 202211
Hi there,
Since around 2022-11, I am unable to change display brightness
of the display of a Framework laptop (Intel i5-1135G7, Iris
Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port)
& "acpi_video" (FreeBSD) kernel module.
Earlier I was able to change brightness via "hw.acpi.video" MIB ...
# - Need to have both "i915kms" & "acpi_video" modules already loaded.
#
# 20221120 - These MIBs do not work anymore as they are missing.
hw.acpi.video.lcd0.economy=10
hw.acpi.video.lcd0.fullpower=40
hw.acpi.video.lcd0.brightness=15
... now the whole of "hw.acpi.video" stub is missing. Nothing has
changed in terms of how/when "i915kms" & "acpi_video" are loaded (via
"kld_list" variable via "/etc/rc.conf" in that order).
What am I missing?
- parv
## /etc/rc.conf :
clear_tmp_enable="YES"
sendmail_enable="NONE"
sshd_enable="YES"
zfs_enable="YES"
dumpdev="AUTO"
hostname="luna"
devmatch_blacklist="ng_ubt"
devmatch_blacklist="$devmatch_blacklist if_iwlwifi"
moused_enable="YES"
kld_list="filemon"
# As of 20220316 on 14-CURRENT order of values assigned to a variable
matters
# enough that assigning "acpi_video" after "i915kms" is sufficient.
#
# WARNING - After loading 'acpi_video' module, brightness suddenly increases
# blindingly.
#
# XXX: If i915kms does not load properly on boot, say after world install,
will
# see a blank screen & Ctrl-Alt-{Delete,Backspace,Escape} do not seem
to
# work; need a hard reboot.
#
# 20230120 - Since around 2022-11 or 2022-12, order has no effect on
brightness.
kld_list="$kld_list i915kms"
kld_list="$kld_list acpi_video"
# Attemp to maximize battery life.
power_profile='economy'
economy_cx_lowest='Cmax'
performance_cx_lowest='C2'
wifibox_enable="YES"
defaultrouter="10.0.0.1"
defaultroot_delay="10"
ifconfig_wifibox0="SYNCDHCP"
background_dhclient_wifibox0="YES"
ntpd_enable="YES"
ntpd_flags="-G"
dbus_enable="YES"
smartd_enable="YES"
## /etc/sysctl.conf :
kern.randompid=1
vfs.usermount=1
kern.vt.kbd_halt=1
kern.vt.kbd_poweroff=1
kern.vt.kbd_reboot=1
kern.vt.kbd_debug=1
kern.vt.kbd_panic=1
vfs.zfs.arc.max=30064771072
dev.hwpstate_intel.0.epp=70
dev.hwpstate_intel.1.epp=70
dev.hwpstate_intel.2.epp=100
dev.hwpstate_intel.3.epp=100
dev.hwpstate_intel.4.epp=100
dev.hwpstate_intel.5.epp=100
dev.hwpstate_intel.6.epp=100
dev.hwpstate_intel.7.epp=100
kern.timecounter.hardware='HPET'
hw.acpi.lid_switch_state='S5'
hw.acpi.sleep_button_state='S5'
# 'acpi_video' module needs to be loaded after 'i915kms' module to have LCD
# brightness related MIBs -- hw.acpi.lcd0.* -- to have any effect. This has
# been an issue since 2014, see PR 195116,
# <https://bugs.freebsd.org/bugzilla/show_bug_cgi?id=195116>.
#
# As of 20220316 on 14-CURRENT order of values assigned to a variable
matters
# enough that assigning "acpi_video" after "i915kms" to "$kld_list" in
# "/etc/rc.conf" is sufficient.
#
# WARNING - After loading 'acpi_video' module, brightness suddenly increases
# blindinly.
#
# Default of 50 for 'hw.acpi.video.lcd0.brightness' rather too bright; 100
is
# blinding.
# - Need to have both "i915kms" & "acpi_video" modules already loaded.
#
# 20221120 - These MIBs do not work anymore as they are missing.
#hw.acpi.video.lcd0.economy=10
#hw.acpi.video.lcd0.fullpower=40
#hw.acpi.video.lcd0.brightness=15
# Power management with "i915kms" module from "drm-devel-kmod" (14-CURRENT)
# package.
# - only in "/boot/loader.conf" ...
#
# compat.linuxkpi.i915_enable_dc=2
# compat.linuxkpi.i915_disable_power_well=<-1|0|1>
#
# ... that means need to load i915kms in "/boot/loader.conf" too.?
#
compat.linuxkpi.i915_fastboot=1
compat.linuxkpi.i915_enable_fbc=1
## /boot/loader.conf :
cryptodev_load="YES"
zfs_load="YES"
kern.msgbufsize=1146880
ums_load="YES"
hms_load="YES"
hw.vga.textmode=0
kern.vty=vt
# Need to load after i915kms module to have effect; so is loaded via
# /etc/rc.conf instead by adding it to $kld_list after "i915kms" as in
# 'kld_list="i915kms acpi_video"'.
#acpi_video_load="YES"
machdep.hwpstate_pkg_ctrl=0
coretemp_load="YES"
## From "/etc/rc.conf" ...
# Power management with "i915kms" module from "drm-devel-kmod" (14-CURRENT)
# package.
# - only in "/boot/loader.conf" ...
#
# compat.linuxkpi.i915_enable_dc=2
# compat.linuxkpi.i915_disable_power_well=<-1|0|1>
#
# ... that means need to load i915kms in "/boot/loader.conf" too.?
#
#compat.linuxkpi.i915_fastboot=1
#compat.linuxkpi.i915_enable_fbc=1
hw.pci.do_power_nodriver=2
Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211
I should have requested in OP to CC to me as I have subscribed to -current@ list without receiving email. So here is my attempt to craft a reponse from the web page ... https://lists.freebsd.org/archives/freebsd-current/2023-January/003142.html > Oleksandr Kryvulia wrote on 20230131-092359 UTC > > 31.01.23 09:52, parv/FreeBSD пише: > > > > Since around 2022-11, I am unable to change display brightness > > of the display of a Framework laptop (Intel i5-1135G7, Iris > > Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port) > > & "acpi_video" (FreeBSD) kernel module. > > > > Earlier I was able to change brightness via "hw.acpi.video" MIB ... > > > > # - Need to have both "i915kms" & "acpi_video" modules already loaded. > > # > > # 20221120 - These MIBs do not work anymore as they are missing. > > hw.acpi.video.lcd0.economy=10 > > hw.acpi.video.lcd0.fullpower=40 > > hw.acpi.video.lcd0.brightness=15 ... > Does backlight(8) works for you? Thanks for the clue. It does! It does ... - I get the same number back via "backlight" without any arguments as what I gave it earlier. There was no reporting of value being subtracted by one; - with 0, everything was near-black, dark enough for not being able to read anything on the console; - with 100, screen was surely damn bright *oh my eyes* - unlike Poul-Hennig K's experience ... https://lists.freebsd.org/archives/freebsd-current/2023-January/003143.html ... when running with & without AC (for short periods) I did not see any change in "backlight" behaviour. The brightness did not change unless I had changed it myself. Thanks again. FreeBSD here is ... FreeBSD luna 14.0-CURRENT FreeBSD 14.0-CURRENT #6 main-n260169-34ac629b40e6: Fri Jan 20 07:05:01 HST 2023 root@luna:/build/world/freebsd/src/amd64.amd64/sys/GENERIC-Light amd64 - parv --
Re: find(1): I18N gone wild? [[:alpha:]] not a substitute to refer 26 English letters A-Z
Wrote Dimitry Andric on Fri, 21 Apr 2023 10:38:05 UTC (via https://lists.freebsd.org/archives/freebsd-current/2023-April/003556.html ) > > ... However, I have read that with unicode, you should *never* > use [A-Z] or [0-9], but character classes instead. That seems to give > both files on macOS and Linux with [[:alpha:]]: ... Subject to the locale, problem with that is "[[:alpha:]]" will match more than 26 English letters "A" through "Z" (besides also matching lower case "a" through "z") even if none of 26 * 2 English alphabets appear in a string. - parv
Stuck on ERROR-tried-to-rebuild-during-make-install, from 1cebc9298cf to b98fbf3781, or from 9fbeeb6e3831 to dfa1982352ee
-o root -g wheel -m 444 crtbeginT.o /usr/lib/crtbeginT.o
--- crt1_c.o ---
ccache: error: Could not find compiler "cc" in PATH
--- gcrt1_c.o ---
ccache: error: Could not find compiler "cc" in PATH
--- Scrt1_c.o ---
ccache: error: Could not find compiler "cc" in PATH
--- crt1_c.o ---
*** [crt1_c.o] Error code 1
make[6]: stopped in /freebsd/src/lib/csu/amd64
--- Scrt1_c.o ---
*** [Scrt1_c.o] Error code 1
make[6]: stopped in /freebsd/src/lib/csu/amd64
--- gcrt1_c.o ---
*** [gcrt1_c.o] Error code 1
...
/etc/{make,src}*conf: attached 9fbeeb6e3831-to-dfa1982352ee.etc.list
- parv
1cebc9298cf-to-b98fbf3781.etc.list
Description: Binary data
9fbeeb6e3831-to-dfa1982352ee.etc.list
Description: Binary data
Re: Stuck on ERROR-tried-to-rebuild-during-make-install, from 1cebc9298cf to b98fbf3781, or from 9fbeeb6e3831 to dfa1982352ee
*sigh* Attachments did not seem to make the list archive ...
On Thu, Jun 15, 2023 at 1:14 AM parv/FreeBSD wrote:
> I am stuck in "installworld" step due to
> ERROR-tried-to-rebuild-during-make-install when going
> from 1cebc9298cf to b98fbf3781 on one host, or from
> 9fbeeb6e3831 to dfa1982352ee on another host.
>
> What should I be looking for?
>
>
> 1cebc9298cf-to-b98fbf3781:
>
...
> /etc/{make,src}*conf: attached 1cebc9298cf-to-b98fbf3781.etc.list
>
# FILE /14m/etc/make.conf
SRC_BASE= /freebsd/src
PORTSDIR= /freebsd/ports
PACKAGES= /freebsd/pkg-save
WRKDIRPREFIX= /build/ports
BATCH= yes
MAKE_JOBS_NUMBER= 10
MAKE_JOBS_NUMBER_LIMIT= 11
DEFAULT_VERSIONS+= python3=3.11 python=3.11
OPTIONS_UNSET+= HAL
OPTIONS_UNSET+= WAYLAND VIDEO_WAYLAND PLATFORM_WAYLAND
OPTIONS_UNSET+= DEBUG TEST DOXYGEN
OPTIONS_UNSET+= HAL
.if ${.CURDIR:M/*/*/www/lynx*}
MAKE_JOBS_UNSAFE= yes
.endif
# FILE /14m/etc/src-env.conf
WITH_META_MODE= yes
MAKEOBJDIRPREFIX?= /build/world
CCACHE_DIR= /build/ccache
# FILE /14m/etc/src.conf
SRC_BASE= /freebsd/src
PORTSDIR= /freebsd/ports
PACKAGES= /freebsd/pkg-save
WRKDIRPREFIX= /build/ports
WITHOUT_FINGER= yes
WITHOUT_FLOPPY= yes
WITHOUT_GAMES= yes
WITHOUT_TCSH= yes
WITHOUT_LIB32= yes
WITHOUT_ATM= yes
WITHOUT_CXGBETOOL= yes
WITHOUT_IPFILTER= yes
WITHOUT_OFED= yes
WITHOUT_PPP= yes
WITH_BHYVE_SNAPSHOT= yes
WITH_EXTRA_TCP_STACKS= yes
WITH_SORT_THREADS= yes
WITH_CTF= yes
WITH_INIT_ALL_ZERO= yes
WITH_KERNEL_RETPOLINE= yes
WITH_RETPOLINE= yes
KERNCONF= GENERIC-Light
WITH_MALLOC_PRODUCTION= yes
WITHOUT_LLVM_ASSERTIONS= yes
9fbeeb6e3831-to-dfa1982352ee:
> ...
>
/etc/{make,src}*conf: attached 9fbeeb6e3831-to-dfa1982352ee.etc.list
>
# FILE: /14u/etc/make.conf
WITH_CCACHE_BUILD= yes
CCACHE_DIR= /aux-build/ccache-14
SRC_BASE= /freebsd/src
KERNCONF= GENERIC-NODEBUG
PORTSDIR= /freebsd/ports
DISTDIR= /freebsd/ports-distfiles
WRKDIRPREFIX= /aux-build/ports
PACKAGES= /freebsd/saved-packages
MAKE_JOBS_NUMBER= 9
MAKE_JOBS_NUMBER_LIMIT= 10
BATCH= yes
WITHOUT_INFO= yes
WITHOUT_JAVA= yes
OPTIONS_UNSET+= EXAMPLES INFO JAVA DEBUG
OPTIONS_SET+= NLS ICONV IDN
OPTIONS_SET+= DOCS
OPTIONS_SET+= NCURSES
DEFAULT_VERSIONS+= python=3.11 python3=3.11
# FILE: /14u/etc/src-env.conf
WITH_META_MODE= yes
MAKEOBJDIRPREFIX?= /aux-build/freebsd-14
# FILE: /14u/etc/src.conf
WITHOUT_ATM= yes
WITHOUT_FINGER= yes
WITHOUT_FLOPPY= yes
WITHOUT_GAMES= yes
WITHOUT_PPP= yes
WITHOUT_IPFILTER= yes
WITHOUT_SHAREDOCS= yes
WITHOUT_LIB32= yes
WITHOUT_TCSH= yes
WITH_LLDB= yes
WITH_BIND_NOW= yes
WITH_CTF= yes
WITH_DMAGENT= yes
WITH_RETPOLINE= yes
WITH_KERNEL_RETPOLINE= yes
WITH_BHYVE_SNAPSHOT= yes
WITH_HYPERV= yes
WITH_NVME= yes
WITH_INIT_ALL_ZERO= yes
WITH_EXTRA_TCP_STACKS= yes
Re: Stuck on ERROR-tried-to-rebuild-during-make-install- How to move past?
On Thu, Jun 15, 2023 at 1:14 AM parv/FreeBSD wrote:
> Hi there,
>
> I am stuck in "installworld" step due to
> ERROR-tried-to-rebuild-during-make-install when going
> from 1cebc9298cf to b98fbf3781 on one host, or from
> 9fbeeb6e3831 to dfa1982352ee on another host.
>
> What should I be looking for?
>
>
> 1cebc9298cf-to-b98fbf3781:
> log:
> ...
> install -d -m 0755 -o root -g wheel /boot
> install -o root -g wheel -m 444 loader.help.efi /boot/loader.help.efi
> cc -target x86_64-unknown-freebsd14.0
> --sysroot=/build/world/freebsd/src/amd64.amd64/tmp
> -B/build/world/freebsd/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-common
> -Wformat -fshort-wchar -mno-red-zone -nostdinc
> -I/build/world/freebsd/src/amd64.amd64/stand/libsa
> -I/freebsd/src/stand/libsa -D_STANDALONE -I/freebsd/src/sys
> -Ddouble=jagged-little-pill -Dfloat=floaty-mcfloatface -ffunction-sections
> -fdata-sections -DLOADER_GELI_SUPPORT -I/freebsd/src/stand/libsa/geli
> -DLOADER_DISK_SUPPORT -ffreestanding -mno-mmx -mno-sse -mno-avx -mno-avx2
> -msoft-float -fPIC -mno-red-zone -mno-relax -I. -Iinclude
> -I/freebsd/src/stand/efi/loader_4th/../loader
> -I/freebsd/src/stand/libsa/zfs -I/freebsd/src/sys/contrib/openzfs/include
> -I/freebsd/src/sys/contrib/openzfs/include/os/freebsd/zfs -DEFI_ZFS_BOOT
> -fPIC -I/freebsd/src/stand/efi/loader_4th
> -I/freebsd/src/stand/efi/loader_4th/arch/amd64
> -I/freebsd/src/stand/efi/include -I/freebsd/src/stand/efi/include/amd64
> -I/freebsd/src/sys/contrib/dev/acpica/include
> -I/freebsd/src/stand/i386/libi386 -DEFI -I/freebsd/src/stand/common -fPIC
> -I/freebsd/src/stand/ficl -I/freebsd/src/stand/ficl/amd64
> -I/freebsd/src/stand/common -DBF_DICTSIZE=3 -DLOADER_MSDOS_SUPPORT
> -DLOADER_UFS_SUPPORT -DLOADER_NET_SUPPORT -DLOADER_GPT_SUPPORT
> -DLOADER_MBR_SUPPORT -DLOADER_ZFS_SUPPORT -I/freebsd/src/stand/libsa/zfs
> -I/freebsd/src/sys/cddl/boot/zfs
> -I/freebsd/src/sys/cddl/contrib/opensolaris/uts/common
> -DHELP_FILENAME=\"loader.help.efi\" -mretpoline
> -ftrivial-auto-var-init=zero
> -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang
> -g -gz=zlib -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Werror
> -Wno-pointer-sign -Wdate-time -Wno-empty-body -Wno-string-plus-int
> -Wno-unused-const-variable -Wno-error=unused-but-set-variable
> -Wno-error=array-parameter -Wno-error=deprecated-non-prototype
> -Wno-error=unused-but-set-parameter -Wno-tautological-compare
> -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function
> -Wno-enum-conversion -Wno-unused-local-typedef
> -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum
> -Wno-knr-promoted-parameter -Wno-parentheses -Oz -Qunused-arguments
> ERROR-tried-to-rebuild-during-make-install
> -c /freebsd/src/stand/efi/loader_4th/../loader/efiserialio.c -o
> efiserialio.o
> /tmp/install.PjBzUKhv0k/sh: cc: not found
> *** Error code 127
>
> Stop.
> make[6]: stopped in /freebsd/src/stand/efi/loader_4th
> ...
>
> /etc/{make,src}*conf: attached 1cebc9298cf-to-b98fbf3781.etc.list
>
...
Also asked at https://mastodon.social/@parvXm/110598357680164603
where I note that ...
ERROR-tried-to-rebuild-during-make-install
... was introduced in c 2017 per
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212877#c21 .
Re: Stuck on ERROR-tried-to-rebuild-during-make-install- How to move past?
On Sun, Jun 25, 2023 at 5:10 PM Kyle Evans wrote:
Hi Kyle,
Thanks for the response.
On 6/24/23 04:06, parv/FreeBSD wrote:
> > On Thu, Jun 15, 2023 at 1:14 AM parv/FreeBSD wrote:
> >
> > Hi there,
> >
> > I am stuck in "installworld" step due to
> > ERROR-tried-to-rebuild-during-make-install when going
> > from 1cebc9298cf to b98fbf3781 on one host, or from
> > 9fbeeb6e3831 to dfa1982352ee on another host.
> >
> > What should I be looking for?
> >
> >
> > 1cebc9298cf-to-b98fbf3781:
> > log:
> > ...
> > install -d -m 0755 -o root -g wheel /boot
> > install -o root -g wheel -m 444 loader.help.efi
> /boot/loader.help.efi
>
Tried again but failed at this point again ...
> > cc -target x86_64-unknown-freebsd14.0
> > --sysroot=/build/world/freebsd/src/amd64.amd64/tmp
> > -B/build/world/freebsd/src/amd64.amd64/tmp/usr/bin -O2 -pipe
> > -fno-common -Wformat -fshort-wchar -mno-red-zone -nostdinc
> > -I/build/world/freebsd/src/amd64.amd64/stand/libsa
> > -I/freebsd/src/stand/libsa -D_STANDALONE -I/freebsd/src/sys
> > -Ddouble=jagged-little-pill -Dfloat=floaty-mcfloatface
> > -ffunction-sections -fdata-sections -DLOADER_GELI_SUPPORT
> > -I/freebsd/src/stand/libsa/geli -DLOADER_DISK_SUPPORT -ffreestanding
> > -mno-mmx -mno-sse -mno-avx -mno-avx2 -msoft-float -fPIC
> > -mno-red-zone -mno-relax -I. -Iinclude
> > -I/freebsd/src/stand/efi/loader_4th/../loader
> > -I/freebsd/src/stand/libsa/zfs
> > -I/freebsd/src/sys/contrib/openzfs/include
> > -I/freebsd/src/sys/contrib/openzfs/include/os/freebsd/zfs
> > -DEFI_ZFS_BOOT -fPIC -I/freebsd/src/stand/efi/loader_4th
> > -I/freebsd/src/stand/efi/loader_4th/arch/amd64
> > -I/freebsd/src/stand/efi/include
> > -I/freebsd/src/stand/efi/include/amd64
> > -I/freebsd/src/sys/contrib/dev/acpica/include
> > -I/freebsd/src/stand/i386/libi386 -DEFI -I/freebsd/src/stand/common
> > -fPIC -I/freebsd/src/stand/ficl -I/freebsd/src/stand/ficl/amd64
> > -I/freebsd/src/stand/common -DBF_DICTSIZE=3
> > -DLOADER_MSDOS_SUPPORT -DLOADER_UFS_SUPPORT -DLOADER_NET_SUPPORT
> > -DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT -DLOADER_ZFS_SUPPORT
> > -I/freebsd/src/stand/libsa/zfs -I/freebsd/src/sys/cddl/boot/zfs
> > -I/freebsd/src/sys/cddl/contrib/opensolaris/uts/common
> > -DHELP_FILENAME=\"loader.help.efi\" -mretpoline
> > -ftrivial-auto-var-init=zero
> >
> -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang
> -g -gz=zlib -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Werror
> -Wno-pointer-sign -Wdate-time -Wno-empty-body -Wno-string-plus-int
> -Wno-unused-const-variable -Wno-error=unused-but-set-variable
> -Wno-error=array-parameter -Wno-error=deprecated-non-prototype
> -Wno-error=unused-but-set-parameter -Wno-tautological-compare
> -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function
> -Wno-enum-conversion -Wno-unused-local-typedef
> -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum
> -Wno-knr-promoted-parameter -Wno-parentheses -Oz -Qunused-arguments
> ERROR-tried-to-rebuild-during-make-install -c
> /freebsd/src/stand/efi/loader_4th/../loader/efiserialio.c -o efiserialio.o
> > /tmp/install.PjBzUKhv0k/sh: cc: not found
> > *** Error code 127
> >
> > Stop.
> > make[6]: stopped in /freebsd/src/stand/efi/loader_4th
> > ...
> >
> > /etc/{make,src}*conf: attached 1cebc9298cf-to-b98fbf3781.etc.list
> >
> > ...
> >
> > Also asked at https://mastodon.social/@parvXm/110598357680164603
> > <https://mastodon.social/@parvXm/110598357680164603>
> > where I note that ...
> >
> > ERROR-tried-to-rebuild-during-make-install
> >
> > ... was introduced in c 2017 per
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212877#c21
> > <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212877#c21> .
> >
>
> This error indicates that for some reason we're trying to build during
> the install phase; either tree was updated since last build, messed up
> timestamps on build artifacts, messed up clock, etc. Whatever the case
> may be, make(1) sees the build output of this as out-of-date.
>
Thanks for the pointers.
I had tried again with ...
- checked that the time has been set correctly both during
buildworld+kernel (multi-user) & installworld (single user);
- verified that all the object, source, & ccache directory paths
were correct; and the src/ commit used to build did not change
... still failed as I noted earlier. I checked the (modification)
time of /boot files, which looked ok to me.
Right now I am building without ccache.
If that would fail, then will try without "meta mode" in addition.
If that would also fail, then I would not know what else to do.
- parv
