[PATCH] build: Config-images: build ISO, VMDK and VDI for x86
These images are of interested for some cloud/VM people, build them by default when running the buildbot. Signed-off-by: Paul Spooren --- config/Config-images.in | 3 +++ 1 file changed, 3 insertions(+) diff --git a/config/Config-images.in b/config/Config-images.in index 92720fb84d..ea50d7d399 100644 --- a/config/Config-images.in +++ b/config/Config-images.in @@ -259,18 +259,21 @@ menu "Target Images" bool "Build LiveCD image (ISO)" depends on TARGET_x86 depends on GRUB_IMAGES || GRUB_EFI_IMAGES + default BUILDBOT config VDI_IMAGES bool "Build VirtualBox image files (VDI)" depends on TARGET_x86 depends on GRUB_IMAGES || GRUB_EFI_IMAGES select PACKAGE_kmod-e1000 + default BUILDBOT config VMDK_IMAGES bool "Build VMware image files (VMDK)" depends on TARGET_x86 depends on GRUB_IMAGES || GRUB_EFI_IMAGES select PACKAGE_kmod-e1000 + default BUILDBOT config TARGET_IMAGES_GZIP bool "GZip images" -- 2.30.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH buildbot] Bump to latest Buildbot release 3.3.0
See changelog: https://github.com/buildbot/buildbot/releases/tag/v3.3.0 Signed-off-by: Paul Spooren --- .gitlab-ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 07a0407..5b6f6eb 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,5 +1,5 @@ variables: - BUILDBOT_VERSION: 3.2.0 + BUILDBOT_VERSION: 3.3.0 OPENWRT_VERSION: $CI_COMMIT_SHORT_SHA include: -- 2.30.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH buildbot 2/2] docker: install `mkisofs` to worker container
x86 targets allow the creation of ISO images, however this is not possible because the `mkisofs` is missing. Install it. Signed-off-by: Paul Spooren --- docker/buildworker/Dockerfile | 1 + 1 file changed, 1 insertion(+) diff --git a/docker/buildworker/Dockerfile b/docker/buildworker/Dockerfile index fdbae1f..049d20f 100644 --- a/docker/buildworker/Dockerfile +++ b/docker/buildworker/Dockerfile @@ -25,6 +25,7 @@ RUN \ libelf-dev \ libncurses5-dev \ locales \ + mkisofs \ pv \ pwgen \ python \ -- 2.30.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH buildbot 1/2] docker: sort installed packages alphabetically
Signed-off-by: Paul Spooren --- docker/buildmaster/Dockerfile | 2 +- docker/buildworker/Dockerfile | 12 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docker/buildmaster/Dockerfile b/docker/buildmaster/Dockerfile index 28dc9ed..b2134ce 100644 --- a/docker/buildmaster/Dockerfile +++ b/docker/buildmaster/Dockerfile @@ -19,10 +19,10 @@ RUN \ gosu \ libncurses5-dev \ locales \ - signify-openbsd \ pv \ pwgen \ python3-pip \ + signify-openbsd \ wget && \ apt-get clean && \ localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8 diff --git a/docker/buildworker/Dockerfile b/docker/buildworker/Dockerfile index 9be02ec..fdbae1f 100644 --- a/docker/buildworker/Dockerfile +++ b/docker/buildworker/Dockerfile @@ -21,20 +21,20 @@ RUN \ gcc-multilib \ git-core \ gosu \ - libncurses5-dev \ - libelf-dev \ libdw-dev \ + libelf-dev \ + libncurses5-dev \ locales \ - rsync \ - signify-openbsd \ - subversion \ - swig \ pv \ pwgen \ python \ python3 \ python3-pip \ qemu-utils \ + rsync \ + signify-openbsd \ + subversion \ + swig \ unzip \ wget && \ apt-get clean && \ -- 2.30.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2] iproute2: m_xt.so depends on dynsyms.list
When doing parallel build on a fast machine with bottleneck in i/o,
m_xt.so may start linking faster than dynsyms.list gets populated,
resulting in error:
ld:dynsyms.list:0: syntax error in dynamic list
Fix this by adding dynsyms.list as make dependency to m_xt.so
Described also here:
https://bugs.openwrt.org/index.php?do=details_id=3353
Change from v1:
- add dynsysms.list dependancy only when shared libs are enabled
Signed-off-by: Roman Yeryomin
Fixes: FS#3353
---
.../utils/iproute2/patches/175-reduce-dynamic-syms.patch | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
a/package/network/utils/iproute2/patches/175-reduce-dynamic-syms.patch
b/package/network/utils/iproute2/patches/175-reduce-dynamic-syms.patch
index da961a183b..c3892e5a0e 100644
--- a/package/network/utils/iproute2/patches/175-reduce-dynamic-syms.patch
+++ b/package/network/utils/iproute2/patches/175-reduce-dynamic-syms.patch
@@ -26,13 +26,14 @@
q_atm.so: q_atm.c
$(QUIET_CC)$(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) -shared -fpic -o
q_atm.so q_atm.c -latm
-@@ -205,4 +206,15 @@ static-syms.h: $(wildcard *.c)
+@@ -205,4 +206,16 @@ static-syms.h: $(wildcard *.c)
sed -n '/'$$s'[^ ]* =/{s:.* \([^ ]*'$$s'[^ ]*\) .*:extern char
\1[] __attribute__((weak)); if (!strcmp(sym, "\1")) return \1;:;p}' $$files ; \
done > $@
+else
+
+tc: dynsyms.list
++m_xt.so: dynsyms.list
+dynsyms.list: $(wildcard *.c)
+ files="$(filter-out $(patsubst %.so,%.c,$(TCSO)), $^)" ; \
+ echo "{" > $@ ; \
--
2.25.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] octeontx: add linux 5.10 testing kernel support
> > [snipped] > > > +CONFIG_EXT4_FS=y > > +CONFIG_EXT4_FS_POSIX_ACL=y > > +CONFIG_F2FS_FS=y > > +CONFIG_FANOTIFY=y > > +CONFIG_FAT_FS=y > > Do all of these filesystems have to be built-in? We have config > options for them. I don't think so. I took the kernel 5.4 config as a template, because I didn't want to break things for others when upgrading to 5.10. But I agree, there is no reason for a default buil-in. > > [snipped] > > > +CONFIG_HZ=250 > > Why 250 Hz? Does the 100 Hz all other targets use cause any > measurable > increase in latency? > [snipped] I did not notice this changed. The config I made for 5.10 was before your commit 3326b5e75c277b4fac21bffd2085df4aa40d2775 which changed the default frequency to 100 Hz. There should be no issue with 100 Hz on octecontx, but I will confirm this with new builds on my test devices. > > > +CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y > > CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y might not be a performance win, > especially with only 1 GiB of RAM. Should be measured, otherwise > MADVISE should be selected instead. Same here, it was selected in the 5.4 kernel config and I have only run tested with this option so far. Let me do some benchmarking with MADVISE before we continue here ... > > Best regards, > Rui > -- Regards Daniel Danzberger embeDD GmbH, Alter Postplatz 2, CH-6370 Stans ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] octeontx: add linux 5.10 testing kernel support
Hi again, Daniel, On Fri, 3 Sept 2021 at 12:46, Daniel Danzberger wrote: > [snipped] > +CONFIG_EXT4_FS=y > +CONFIG_EXT4_FS_POSIX_ACL=y > +CONFIG_F2FS_FS=y > +CONFIG_FANOTIFY=y > +CONFIG_FAT_FS=y Do all of these filesystems have to be built-in? We have config options for them. [snipped] > +CONFIG_HZ=250 Why 250 Hz? Does the 100 Hz all other targets use cause any measurable increase in latency? [snipped] > +CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=y might not be a performance win, especially with only 1 GiB of RAM. Should be measured, otherwise MADVISE should be selected instead. Best regards, Rui ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] octeontx: add linux 5.10 testing kernel support
Changes from 5.4 to 5.10: - - patches from 5.4 are all upstream for 5.10 execpt for 0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch - disable block device data integrity (DIF/DIX/T10) in default config (CONFIG_BLK_DEV_INTEGRITY) This feature is only supported by: - Enterprise SAS/SCSI HBAs and Disks - Software raid - NVMEs with metadata capabilities (most don't have this) None of which are part of any octeontx boards. - arm64 TEXT_OFFSET (0x8) has been removed after 5.4 This will break Uimages with kernel load addresses that aren't 2MiB aligned any longer. Resulting in the kernel silently fail to boot. For Gatworks newport boards for example, the uimage kernel load and execute address is 0x2008. These need to be changed to 0x2000 when running kernels beyond 5.4. Tested-on: Gateworks Newport GW64xx Signed-off-by: Daniel Danzberger --- target/linux/octeontx/Makefile| 1 + target/linux/octeontx/config-5.10 | 430 ++ ...r-Gateworks-PLX-PEX860x-switch-with-.patch | 59 +++ 3 files changed, 490 insertions(+) create mode 100644 target/linux/octeontx/config-5.10 create mode 100644 target/linux/octeontx/patches-5.10/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch diff --git a/target/linux/octeontx/Makefile b/target/linux/octeontx/Makefile index c30799b744..44bbc76a43 100644 --- a/target/linux/octeontx/Makefile +++ b/target/linux/octeontx/Makefile @@ -10,6 +10,7 @@ BOARDNAME:=Octeon-TX FEATURES:=targz pcie gpio rtc usb fpu KERNEL_PATCHVER:=5.4 +KERNEL_TESTING_PATCHVER:=5.10 define Target/Description Build images for Octeon-TX CN80XX/CN81XX based boards diff --git a/target/linux/octeontx/config-5.10 b/target/linux/octeontx/config-5.10 new file mode 100644 index 00..8b3a7f68b2 --- /dev/null +++ b/target/linux/octeontx/config-5.10 @@ -0,0 +1,430 @@ +CONFIG_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_ARCH_HIBERNATION_HEADER=y +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_KEEP_MEMBLOCK=y +CONFIG_ARCH_MMAP_RND_BITS=18 +CONFIG_ARCH_MMAP_RND_BITS_MAX=33 +CONFIG_ARCH_MMAP_RND_BITS_MIN=18 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=11 +CONFIG_ARCH_PROC_KCORE_TEXT=y +CONFIG_ARCH_SELECT_MEMORY_MODEL=y +CONFIG_ARCH_SPARSEMEM_DEFAULT=y +CONFIG_ARCH_SPARSEMEM_ENABLE=y +CONFIG_ARCH_STACKWALK=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +CONFIG_ARCH_THUNDER=y +CONFIG_ARM64=y +CONFIG_ARM64_4K_PAGES=y +CONFIG_ARM64_CNP=y +CONFIG_ARM64_CRYPTO=y +CONFIG_ARM64_ERRATUM_1165522=y +CONFIG_ARM64_ERRATUM_1286807=y +CONFIG_ARM64_ERRATUM_819472=y +CONFIG_ARM64_ERRATUM_824069=y +CONFIG_ARM64_ERRATUM_826319=y +CONFIG_ARM64_ERRATUM_827319=y +CONFIG_ARM64_ERRATUM_843419=y +CONFIG_ARM64_HW_AFDBM=y +CONFIG_ARM64_MODULE_PLTS=y +CONFIG_ARM64_PAGE_SHIFT=12 +CONFIG_ARM64_PAN=y +CONFIG_ARM64_PA_BITS=48 +CONFIG_ARM64_PA_BITS_48=y +CONFIG_ARM64_PTR_AUTH=y +CONFIG_ARM64_SVE=y +CONFIG_ARM64_TAGGED_ADDR_ABI=y +CONFIG_ARM64_UAO=y +CONFIG_ARM64_VA_BITS=48 +# CONFIG_ARM64_VA_BITS_39 is not set +CONFIG_ARM64_VA_BITS_48=y +CONFIG_ARM64_VHE=y +CONFIG_ARM64_WORKAROUND_CLEAN_CACHE=y +CONFIG_ARM64_WORKAROUND_REPEAT_TLBI=y +CONFIG_ARM64_WORKAROUND_SPECULATIVE_AT=y +CONFIG_ARM_AMBA=y +CONFIG_ARM_ARCH_TIMER=y +CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y +CONFIG_ARM_CPUIDLE=y +CONFIG_ARM_GIC=y +CONFIG_ARM_GIC_V2M=y +CONFIG_ARM_GIC_V3=y +CONFIG_ARM_GIC_V3_ITS=y +CONFIG_ARM_GIC_V3_ITS_PCI=y +CONFIG_ARM_PSCI_FW=y +CONFIG_ARM_SBSA_WATCHDOG=y +CONFIG_ATA=y +# CONFIG_ATA_SFF is not set +CONFIG_AUDIT_ARCH_COMPAT_GENERIC=y +CONFIG_BALLOON_COMPACTION=y +CONFIG_BLK_DEV_BSG=y +CONFIG_BLK_DEV_BSGLIB=y +CONFIG_BLK_DEV_LOOP=y +CONFIG_BLK_MQ_PCI=y +CONFIG_BLK_MQ_VIRTIO=y +CONFIG_BLK_PM=y +CONFIG_BLK_SCSI_REQUEST=y +CONFIG_CAVIUM_ERRATUM_22375=y +CONFIG_CAVIUM_ERRATUM_23144=y +CONFIG_CAVIUM_ERRATUM_23154=y +CONFIG_CAVIUM_ERRATUM_27456=y +CONFIG_CAVIUM_ERRATUM_30115=y +CONFIG_CAVIUM_TX2_ERRATUM_219=y +CONFIG_CC_HAVE_STACKPROTECTOR_SYSREG=y +CONFIG_CLKDEV_LOOKUP=y +CONFIG_CLONE_BACKWARDS=y +CONFIG_CMA=y +CONFIG_CMA_ALIGNMENT=8 +CONFIG_CMA_AREAS=7 +# CONFIG_CMA_DEBUG is not set +# CONFIG_CMA_DEBUGFS is not set +CONFIG_CMA_SIZE_MBYTES=16 +# CONFIG_CMA_SIZE_SEL_MAX is not set +CONFIG_CMA_SIZE_SEL_MBYTES=y +# CONFIG_CMA_SIZE_SEL_MIN is not set +# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set +CONFIG_COMMON_CLK=y +CONFIG_COMMON_CLK_CS2000_CP=y +# CONFIG_COMPAT_32BIT_TIME is not set +CONFIG_CONFIGFS_FS=y +CONFIG_CONTIG_ALLOC=y +CONFIG_CPU_IDLE=y +CONFIG_CPU_IDLE_GOV_MENU=y +CONFIG_CPU_IDLE_MULTIPLE_DRIVERS=y +CONFIG_CPU_PM=y +CONFIG_CPU_RMAP=y +CONFIG_CRASH_CORE=y +CONFIG_CRASH_DUMP=y +CONFIG_CRC16=y +CONFIG_CRC7=y +CONFIG_CRC_ITU_T=y +CONFIG_CRC_T10DIF=y +CONFIG_CRYPTO_AES_ARM64=y +CONFIG_CRYPTO_AES_ARM64_CE=y +CONFIG_CRYPTO_AES_ARM64_CE_BLK=y +CONFIG_CRYPTO_AES_ARM64_CE_CCM=y +CONFIG_CRYPTO_ANSI_CPRNG=y +CONFIG_CRYPTO_CRC32=y +CONFIG_CRYPTO_CRC32C=y +CONFIG_CRYPTO_CRCT10DIF=y +CONFIG_CRYPTO_CRYPTD=y +CONFIG_CRYPTO_DRBG=y
Re: [PATCH] octeontx: add linux 5.10 testing kernel support
Hi, forgot that. There were some more redundand symbols. New patch is on the way ... On Fri, 2021-09-03 at 10:26 +0100, Rui Salvaterra wrote: > Hi, Daniel, > > On Fri, 3 Sept 2021 at 10:18, Daniel Danzberger > wrote: > > > > [snipped for context] > > > +CONFIG_RCU_NEED_SEGCBLIST=y > > +CONFIG_RCU_STALL_COMMON=y > > Please refresh your kernel configuration. At least these two symbols > are part of the generic kconfigs. > > Thanks, > Rui > -- Regards Daniel Danzberger embeDD GmbH, Alter Postplatz 2, CH-6370 Stans ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] octeontx: add linux 5.10 testing kernel support
Hi, Daniel, On Fri, 3 Sept 2021 at 10:18, Daniel Danzberger wrote: > [snipped for context] > +CONFIG_RCU_NEED_SEGCBLIST=y > +CONFIG_RCU_STALL_COMMON=y Please refresh your kernel configuration. At least these two symbols are part of the generic kconfigs. Thanks, Rui ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] octeontx: add linux 5.10 testing kernel support
Changes from 5.4 to 5.10: - - patches from 5.4 are all upstream for 5.10 execpt for 0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch - disable block device data integrity (DIF/DIX/T10) in default config (CONFIG_BLK_DEV_INTEGRITY) This feature is only supported by: - Enterprise SAS/SCSI HBAs and Disks - Software raid - NVMEs with metadata capabilities (most don't have this) None of which are part of any octeontx boards. - arm64 TEXT_OFFSET (0x8) has been removed after 5.4 This will break Uimages with kernel load addresses that aren't 2MiB aligned any longer. Resulting in the kernel silently fail to boot. For Gatworks newport boards for example, the uimage kernel load and execute address is 0x2008. These need to be changed to 0x2000 when running kernels beyond 5.4. Tested-on: Gateworks Newport GW64xx Signed-off-by: Daniel Danzberger --- target/linux/octeontx/Makefile| 1 + target/linux/octeontx/config-5.10 | 442 ++ ...r-Gateworks-PLX-PEX860x-switch-with-.patch | 59 +++ 3 files changed, 502 insertions(+) create mode 100644 target/linux/octeontx/config-5.10 create mode 100644 target/linux/octeontx/patches-5.10/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch diff --git a/target/linux/octeontx/Makefile b/target/linux/octeontx/Makefile index c30799b744..44bbc76a43 100644 --- a/target/linux/octeontx/Makefile +++ b/target/linux/octeontx/Makefile @@ -10,6 +10,7 @@ BOARDNAME:=Octeon-TX FEATURES:=targz pcie gpio rtc usb fpu KERNEL_PATCHVER:=5.4 +KERNEL_TESTING_PATCHVER:=5.10 define Target/Description Build images for Octeon-TX CN80XX/CN81XX based boards diff --git a/target/linux/octeontx/config-5.10 b/target/linux/octeontx/config-5.10 new file mode 100644 index 00..baae584300 --- /dev/null +++ b/target/linux/octeontx/config-5.10 @@ -0,0 +1,442 @@ +CONFIG_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_ARCH_HIBERNATION_HEADER=y +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_KEEP_MEMBLOCK=y +CONFIG_ARCH_MMAP_RND_BITS=18 +CONFIG_ARCH_MMAP_RND_BITS_MAX=33 +CONFIG_ARCH_MMAP_RND_BITS_MIN=18 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=11 +CONFIG_ARCH_PROC_KCORE_TEXT=y +CONFIG_ARCH_SELECT_MEMORY_MODEL=y +CONFIG_ARCH_SPARSEMEM_DEFAULT=y +CONFIG_ARCH_SPARSEMEM_ENABLE=y +CONFIG_ARCH_STACKWALK=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +CONFIG_ARCH_THUNDER=y +CONFIG_ARM64=y +CONFIG_ARM64_4K_PAGES=y +CONFIG_ARM64_CNP=y +CONFIG_ARM64_CRYPTO=y +CONFIG_ARM64_ERRATUM_1165522=y +CONFIG_ARM64_ERRATUM_1286807=y +CONFIG_ARM64_ERRATUM_819472=y +CONFIG_ARM64_ERRATUM_824069=y +CONFIG_ARM64_ERRATUM_826319=y +CONFIG_ARM64_ERRATUM_827319=y +CONFIG_ARM64_ERRATUM_843419=y +CONFIG_ARM64_HW_AFDBM=y +CONFIG_ARM64_MODULE_PLTS=y +CONFIG_ARM64_PAGE_SHIFT=12 +CONFIG_ARM64_PAN=y +CONFIG_ARM64_PA_BITS=48 +CONFIG_ARM64_PA_BITS_48=y +CONFIG_ARM64_PTR_AUTH=y +CONFIG_ARM64_SVE=y +CONFIG_ARM64_TAGGED_ADDR_ABI=y +CONFIG_ARM64_UAO=y +CONFIG_ARM64_VA_BITS=48 +# CONFIG_ARM64_VA_BITS_39 is not set +CONFIG_ARM64_VA_BITS_48=y +CONFIG_ARM64_VHE=y +CONFIG_ARM64_WORKAROUND_CLEAN_CACHE=y +CONFIG_ARM64_WORKAROUND_REPEAT_TLBI=y +CONFIG_ARM64_WORKAROUND_SPECULATIVE_AT=y +CONFIG_ARM_AMBA=y +CONFIG_ARM_ARCH_TIMER=y +CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y +CONFIG_ARM_CPUIDLE=y +CONFIG_ARM_GIC=y +CONFIG_ARM_GIC_V2M=y +CONFIG_ARM_GIC_V3=y +CONFIG_ARM_GIC_V3_ITS=y +CONFIG_ARM_GIC_V3_ITS_PCI=y +CONFIG_ARM_PSCI_FW=y +CONFIG_ARM_SBSA_WATCHDOG=y +# CONFIG_ARM_SCMI_PROTOCOL is not set +CONFIG_ATA=y +# CONFIG_ATA_SFF is not set +CONFIG_AUDIT_ARCH_COMPAT_GENERIC=y +CONFIG_BALLOON_COMPACTION=y +CONFIG_BLK_DEV_BSG=y +CONFIG_BLK_DEV_BSGLIB=y +CONFIG_BLK_DEV_LOOP=y +CONFIG_BLK_MQ_PCI=y +CONFIG_BLK_MQ_VIRTIO=y +CONFIG_BLK_PM=y +CONFIG_BLK_SCSI_REQUEST=y +CONFIG_CAVIUM_ERRATUM_22375=y +CONFIG_CAVIUM_ERRATUM_23144=y +CONFIG_CAVIUM_ERRATUM_23154=y +CONFIG_CAVIUM_ERRATUM_27456=y +CONFIG_CAVIUM_ERRATUM_30115=y +CONFIG_CAVIUM_TX2_ERRATUM_219=y +CONFIG_CLKDEV_LOOKUP=y +CONFIG_CLONE_BACKWARDS=y +CONFIG_CMA=y +CONFIG_CMA_ALIGNMENT=8 +CONFIG_CMA_AREAS=7 +# CONFIG_CMA_DEBUG is not set +# CONFIG_CMA_DEBUGFS is not set +CONFIG_CMA_SIZE_MBYTES=16 +# CONFIG_CMA_SIZE_SEL_MAX is not set +CONFIG_CMA_SIZE_SEL_MBYTES=y +# CONFIG_CMA_SIZE_SEL_MIN is not set +# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set +CONFIG_COMMON_CLK=y +CONFIG_COMMON_CLK_CS2000_CP=y +# CONFIG_COMPAT_32BIT_TIME is not set +CONFIG_CONFIGFS_FS=y +CONFIG_CONTIG_ALLOC=y +CONFIG_CPU_IDLE=y +CONFIG_CPU_IDLE_GOV_MENU=y +CONFIG_CPU_IDLE_MULTIPLE_DRIVERS=y +CONFIG_CPU_PM=y +CONFIG_CPU_RMAP=y +CONFIG_CRASH_CORE=y +CONFIG_CRASH_DUMP=y +CONFIG_CRC16=y +CONFIG_CRC7=y +CONFIG_CRC_ITU_T=y +CONFIG_CRC_T10DIF=y +CONFIG_CRYPTO_AEAD=y +CONFIG_CRYPTO_AEAD2=y +CONFIG_CRYPTO_AES_ARM64=y +# CONFIG_CRYPTO_AES_ARM64_BS is not set +CONFIG_CRYPTO_AES_ARM64_CE=y +CONFIG_CRYPTO_AES_ARM64_CE_BLK=y +CONFIG_CRYPTO_AES_ARM64_CE_CCM=y +# CONFIG_CRYPTO_AES_ARM64_NEON_BLK is not set
Re: [OpenWrt-Devel] [PATCH] iproute2: m_xt.so depends on dynsyms.list
On 2021-09-03 02:28, Roman Yeryomin wrote: When doing parallel build on a fast machine with bottleneck in i/o, m_xt.so may start linking faster than dynsyms.list gets populated, resulting in error: ld:dynsyms.list:0: syntax error in dynamic list Fix this by adding dynsyms.list as make dependency to m_xt.so Described also here: https://bugs.openwrt.org/index.php?do=details_id=3353 Signed-off-by: Roman Yeryomin Fixes: FS#3353 --- Please discard this. Making m_xt.so dependant on dynsyms.list unconditionally was bad idea. Will re-send proper version. Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
