Profiled libraries on freebsd-current
If one looks at src.conf(5), one finds WITH_PROFILE Build profiled libraries for use with gprof(8). This option is deprecated and is not present in FreeBSD 14. I assume that the *_p.a libraries will no longer be built and installed on FreeBSD 14 and later. Is this correct? -- Steve
Re: sys/arm/broadcom/bcm2835/bcm2838_xhci.c:184:21: error: variable 'sc' set but not used [-Werror,-Wunused-but-set-variable]
IGNORE. On 2022-Apr-28, at 20:33, Mark Millard wrote: > In attempting to update from main-n253904-4d1ba6febfa7 based to > main-n255108-9fb40baf6043 based, targeting aarch64, the following > code from sys/arm/broadcom/bcm2835/bcm2838_xhci.c was rejected: > > static int > bcm_xhci_attach(device_t dev) > { >struct xhci_softc *sc; >int error; > >sc = device_get_softc(dev); > >bcm_xhci_install_xhci_firmware(dev); > >error = xhci_pci_attach(dev); >return (error); > } > > as follows: > > --- bcm2838_xhci.o --- > /usr/main-src/sys/arm/broadcom/bcm2835/bcm2838_xhci.c:184:21: error: variable > 'sc' set but not used [-Werror,-Wunused-but-set-variable] >struct xhci_softc *sc; > ^ > Building > /usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72/imx_i2c.o > 1 error generated. > *** [bcm2838_xhci.o] Error code 1 > > make[2]: stopped in > /usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 > .ERROR_TARGET='bcm2838_xhci.o' > .ERROR_META_FILE='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72/bcm2838_xhci.o.meta' > .MAKE.LEVEL='2' > MAKEFILE='' > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose > curdirOk=yes' > _ERROR_CMD='cc -target aarch64-unknown-freebsd14.0 > --sysroot=/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp > > -B/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/bin > -c -O2 -pipe -fno-strict-aliasing -g -nostdinc -I. -I/usr/main-src/sys > -I/usr/main-src/sys/contrib/ck/include -I/usr/main-src/sys/contrib/libfdt > -I/usr/main-src/sys/contrib/device-tree/include -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -mcpu=cortex-a72 -DLINUX_DTS_VERSION=\""5.13"\" > -mstack-protector-guard=sysreg -mstack-protector-guard-reg=sp_el0 > -mstack-protector-guard-offset=0 -fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer > -fdebug-prefix-map=./machine=/usr/main-src/sys/arm64/include > -mgeneral-regs-only -ffixed-x18 -ffreestanding -fwrapv -fstack-protector > -Wall -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes > -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign > -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs > -fdiagnostics-show-option -Wno-unknown-pragmas > -Wno-error=tautological-compare -Wno-error=empty-body > -Wno-error=parentheses-equality -Wno-error=unused-function > -Wno-error=pointer-sign -Wno-error=shift-negative-value > -Wno-address-of-packed-member -Wno-format-zero-length -mcpu=cortex-a72 > -std=iso9899:1999 -Werror > /usr/main-src/sys/arm/broadcom/bcm2835/bcm2838_xhci.c; ctfconvert -L VERSION > -g bcm2838_xhci.o;' > .CURDIR='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72' > .MAKE='make' > .OBJDIR='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72' > .TARGETS='all' > DESTDIR='' > LD_LIBRARY_PATH='' > MACHINE='arm64' > MACHINE_ARCH='aarch64' > MAKEOBJDIRPREFIX='' > MAKESYSPATH='/usr/main-src/share/mk' > MAKE_VERSION='20220208' > PATH='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/sbin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/usr/sbin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/usr/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin' > SRCTOP='/usr/main-src' > OBJTOP='/usr/main-src' > .MAKE.MAKEFILES='/usr/main-src/share/mk/sys.mk > /usr/main-src/share/mk/local.sys.env.mk /usr/main-src/share/mk/src.sys.env.mk > /usr/home/root/src.configs/src.conf.CA72-nodbg-clang.aarch64-host > /usr/main-src/share/mk/bsd.mkopt.mk /usr/main-src/share/mk/src.sys.obj.mk > /usr/main-src/share/mk/auto.obj.mk /usr/main-src/share/mk/bsd.suffixes.mk > /usr/home/root/src.configs/make.conf /usr/main-src/share/mk/local.sys.mk > /usr/main-src/share/mk/src.sys.mk /dev/null Makefile > /usr/main-src/sys/conf/kern.pre.mk /usr/main-src/share/mk/bsd.own.mk > /usr/main-src/share/mk/bsd.opts.mk /usr/main-src/share/mk/bsd.cpu.mk > /usr/main-src/share/mk/bsd.compiler.mk /usr/main-src/share/mk/bsd.endian.mk > /usr/main-src/share/mk/bsd.linker.mk /usr/main-src/sys/conf/kern.opts.mk > /usr/main-src/sys/conf/kern.post.mk /usr/main-src/sys/conf/kern.mk' > .PATH='. > /usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72' > 1 error > This is because of my experimental patches for RPi4 related issues. Sorry for the noise. === Mark Millard marklmi at yahoo.com
sys/arm/broadcom/bcm2835/bcm2838_xhci.c:184:21: error: variable 'sc' set but not used [-Werror,-Wunused-but-set-variable]
In attempting to update from main-n253904-4d1ba6febfa7 based to main-n255108-9fb40baf6043 based, targeting aarch64, the following code from sys/arm/broadcom/bcm2835/bcm2838_xhci.c was rejected: static int bcm_xhci_attach(device_t dev) { struct xhci_softc *sc; int error; sc = device_get_softc(dev); bcm_xhci_install_xhci_firmware(dev); error = xhci_pci_attach(dev); return (error); } as follows: --- bcm2838_xhci.o --- /usr/main-src/sys/arm/broadcom/bcm2835/bcm2838_xhci.c:184:21: error: variable 'sc' set but not used [-Werror,-Wunused-but-set-variable] struct xhci_softc *sc; ^ Building /usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72/imx_i2c.o 1 error generated. *** [bcm2838_xhci.o] Error code 1 make[2]: stopped in /usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 .ERROR_TARGET='bcm2838_xhci.o' .ERROR_META_FILE='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72/bcm2838_xhci.o.meta' .MAKE.LEVEL='2' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose curdirOk=yes' _ERROR_CMD='cc -target aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp -B/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/bin -c -O2 -pipe -fno-strict-aliasing -g -nostdinc -I. -I/usr/main-src/sys -I/usr/main-src/sys/contrib/ck/include -I/usr/main-src/sys/contrib/libfdt -I/usr/main-src/sys/contrib/device-tree/include -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -mcpu=cortex-a72 -DLINUX_DTS_VERSION=\""5.13"\" -mstack-protector-guard=sysreg -mstack-protector-guard-reg=sp_el0 -mstack-protector-guard-offset=0 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fdebug-prefix-map=./machine=/usr/main-src/sys/arm64/include -mgeneral-regs-only -ffixed-x18 -ffreestanding -fwrapv -fstack-protector -Wall -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error=tautological-compare -Wno-error=empty-body -Wno-error=parentheses-equality -Wno-error=unused-function -Wno-error=pointer-sign -Wno-error=shift-negative-value -Wno-address-of-packed-member -Wno-format-zero-length -mcpu=cortex-a72 -std=iso9899:1999 -Werror /usr/main-src/sys/arm/broadcom/bcm2835/bcm2838_xhci.c; ctfconvert -L VERSION -g bcm2838_xhci.o;' .CURDIR='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72' .MAKE='make' .OBJDIR='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72' .TARGETS='all' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='arm64' MACHINE_ARCH='aarch64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/usr/main-src/share/mk' MAKE_VERSION='20220208' PATH='/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/sbin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/usr/sbin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/usr/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/bin:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/main-src' OBJTOP='/usr/main-src' .MAKE.MAKEFILES='/usr/main-src/share/mk/sys.mk /usr/main-src/share/mk/local.sys.env.mk /usr/main-src/share/mk/src.sys.env.mk /usr/home/root/src.configs/src.conf.CA72-nodbg-clang.aarch64-host /usr/main-src/share/mk/bsd.mkopt.mk /usr/main-src/share/mk/src.sys.obj.mk /usr/main-src/share/mk/auto.obj.mk /usr/main-src/share/mk/bsd.suffixes.mk /usr/home/root/src.configs/make.conf /usr/main-src/share/mk/local.sys.mk /usr/main-src/share/mk/src.sys.mk /dev/null Makefile /usr/main-src/sys/conf/kern.pre.mk /usr/main-src/share/mk/bsd.own.mk /usr/main-src/share/mk/bsd.opts.mk /usr/main-src/share/mk/bsd.cpu.mk /usr/main-src/share/mk/bsd.compiler.mk /usr/main-src/share/mk/bsd.endian.mk /usr/main-src/share/mk/bsd.linker.mk /usr/main-src/sys/conf/kern.opts.mk /usr/main-src/sys/conf/kern.post.mk /usr/main-src/sys/conf/kern.mk' .PATH='. /usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72' 1 error === Mark Millard marklmi at yahoo.com
Re: ext2fs: WARNING: mount of XXXX denied due to unsupported optional features: needs_recovery
On Thu, Apr 28, 2022 at 1:29 PM Marek Zarychta wrote: > > W dniu 28.04.2022 o 21:21, FreeBSD User pisze: > > Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to > > rescue them and > > store the data on ZFS volumes. Mounting of the HDD doesn't work, FreeBSD > > 12.3 obviously > > lack in some etx2 features, namely "needs_recovery". The kernel reports: > > > > WARNING: mount of da4p3 denied due to unsupported optional features: > > needs_recovery > > > > How can this problem be solved? > > > > Thanks in advance, > > > > oh > > > Probably as the name of the mailing list suggest you should upgrade to > 14.0-CURRENT and maybe run fsck.ext2(8) on this partition to fix it. > > -- > Marek Zarychta > You might also try sysutils/fusefs-ext2 from ports.
Re: ext2fs: WARNING: mount of XXXX denied due to unsupported optional features: needs_recovery
W dniu 28.04.2022 o 21:21, FreeBSD User pisze: Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to rescue them and store the data on ZFS volumes. Mounting of the HDD doesn't work, FreeBSD 12.3 obviously lack in some etx2 features, namely "needs_recovery". The kernel reports: WARNING: mount of da4p3 denied due to unsupported optional features: needs_recovery How can this problem be solved? Thanks in advance, oh Probably as the name of the mailing list suggest you should upgrade to 14.0-CURRENT and maybe run fsck.ext2(8) on this partition to fix it. -- Marek Zarychta
ext2fs: WARNING: mount of XXXX denied due to unsupported optional features: needs_recovery
Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to rescue them and store the data on ZFS volumes. Mounting of the HDD doesn't work, FreeBSD 12.3 obviously lack in some etx2 features, namely "needs_recovery". The kernel reports: WARNING: mount of da4p3 denied due to unsupported optional features: needs_recovery How can this problem be solved? Thanks in advance, oh
Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory"
On Thu, 28 Apr 2022 12:31:06 +0200 Stefan Esser wrote: > Am 28.04.22 um 09:11 schrieb Baptiste Daroussin> It is 2 things, it > is a port problem of maintainers who do not check for > > upgradability of their packages, and it can also been seen as > > something pkg can deal with, but a complicated case, so I don't > > know yet how. > > > > The main issue is a file in vX which becomes a directory in vX+1 > > which goes in the way pkg does extract files to be as atomic as > > possible. > > This case could be caught and dealt with by removing the file or by > moving it out of the way (to a temporary name to allow it to be > recovered if the subsequent steps fail or to be deleted if they > succeed). > > Further special conditions may apply - but since there is no way a > file and directory can exist under the same name (on FreeBSD, at > least), it is safe to assume that the file will not be kept when the > package is installed. The opposite case seems more interesting/problematic. -m -- Michael Gmelin
Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory"
Am 28.04.22 um 09:11 schrieb Baptiste Daroussin> It is 2 things, it is a port problem of maintainers who do not check for > upgradability of their packages, and it can also been seen as something pkg > can > deal with, but a complicated case, so I don't know yet how. > > The main issue is a file in vX which becomes a directory in vX+1 which goes in > the way pkg does extract files to be as atomic as possible. This case could be caught and dealt with by removing the file or by moving it out of the way (to a temporary name to allow it to be recovered if the subsequent steps fail or to be deleted if they succeed). Further special conditions may apply - but since there is no way a file and directory can exist under the same name (on FreeBSD, at least), it is safe to assume that the file will not be kept when the package is installed. Regards, STefan OpenPGP_signature Description: OpenPGP digital signature
Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory"
## Michael Schuster (michaelspriv...@gmail.com): > $subject happened to me just now on current. I researched it on the > internet, Don't look that far, the answer is in UPDATING: 20220426: AFFECTS: users of deskutils/grantleetheme Regards, Christoph -- Spare Space
Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory"
On Wed, Apr 27, 2022 at 08:47:26PM -0700, Chris wrote: > On 2022-04-27 20:40, Michael Schuster wrote: > > Chris, > > > > thx for your response. However > > > > On Thu, Apr 28, 2022 at 4:19 AM Chris wrote: > > > > > > On 2022-04-27 12:59, Michael Schuster wrote: > > > > Hi, > > > > > > > > $subject happened to me just now on current. I researched it on the > > > > internet, the answer to this issue seems to be a universal "uninstall > > > > and install the package" which seems to have worked in all cases I saw > > > > it suggested. > > > > > > > > I'm trying to embed this command into a script and would like to avoid > > > > manual intervention (I have to admit, this is the first time I've > > > > encountered this error in the two years I've been doodling with > > > > FreeBSD again) ... > > > > Is anything more known about this error behaviour, and what I can do > > > > to avoid it? > > > > > > > > TIA > > > > Michael > > > > > > > > PS: in case it matters: the full path shown in the error message is > > > > /usr/local/include/KF5/GrantleeTheme/GrantleeTheme/.pkgtemp.GenericFormatter.qSk5LxEaheWG, > > > > the package being extracted is grantleetheme-22.04.0 > > > This looks more a case for the Maintainer of the GrantleeTheme than for > > > current@ > > > > ... maybe. OTOH, the instances I found mentioned on the 'net are all > > about different packages: > > > > eg: > > https://forums.freebsd.org/threads/pkg-upgrade-fail-to-create-temporary-file.67923/ > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237767 > > > > I feel there's something different at work here than just one > > maintainer's oversight. > You may well be correct. On the surface, to me it looked like a port problem > so I thought > you might get quicker results via it's maintainer. :-) > > Good luck! :-) > > > > Thx > > Michael It is 2 things, it is a port problem of maintainers who do not check for upgradability of their packages, and it can also been seen as something pkg can deal with, but a complicated case, so I don't know yet how. The main issue is a file in vX which becomes a directory in vX+1 which goes in the way pkg does extract files to be as atomic as possible. Best regards, Bapt