RE: Build issues gcc10
Hi again, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Rui Salvaterra > Sent: Dienstag, 14. September 2021 00:29 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org > Subject: Re: Build issues gcc10 > > Hi, Adrian, > > On Mon, 13 Sept 2021 at 23:10, Adrian Schmutzler > wrote: > > > > Just had one try before I went to bed, but it appears the problem is that > cc1plus generated by the toolchain has no execute bit set: I've resolved the thing. It turned out to be a RAM virtualization issue. Read the full story below (pasted here FYI and for documentation): I've been using Hyper-V for virtualization of the relevant systems. Hyper-V provides a "Dynamic Memory" setting where one can set a minimum/maximum RAM value, so memory is provided to the machines "by demand" with some buffer. In addition, there is a "Startup RAM" setting that is used for boot etc. where the integration drivers for Hyper-V are not yet available in the guest system. For all relevant systems, Startup RAM had been set to 2048 MiB, and maximum memory was set to 8G or higher. During further investigation of my build logs, I found that - apart from the error reported here previously - I had another error which occurred earlier in the process. I received collect2: fatal error: ld terminated with signal 9 [Killed] during the following command: g++ -no-pie -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -static-libstdc++ -static-libgcc -o cc1plus \ cp/cp-lang.o c-family/stub-objc.o cp/call.o cp/class.o cp/constexpr.o cp/constraint.o cp/coroutines.o cp/cp-gimplify.o cp/cp-objcp-common.o cp/cp-ubsan.o cp/cvt.o cp/cxx-pretty-print.o cp/decl.o cp/decl2.o cp/dump.o cp/error.o cp/except.o cp/expr.o cp/friend.o cp/init.o cp/lambda.o cp/lex.o cp/logic.o cp/mangle.o cp/method.o cp/name-lookup.o cp/optimize.o cp/parser.o cp/pt.o cp/ptree.o cp/rtti.o cp/search.o cp/semantics.o cp/tree.o cp/typeck.o cp/typeck2.o cp/vtable-class-hierarchy.o attribs.o incpath.o c-family/c-common.o c-family/c-cppbuiltin.o c-family/c-dump.o c-family/c-format.o c-family/c-gimplify.o c-family/c-indentation.o c-family/c-lex.o c-family/c-omp.o c-family/c-opts.o c-family/c-pch.o c-family/c-ppoutput.o c-family/c-pragma.o c-family/c-pretty-print.o c-family/c-semantics.o c-family/c-ada-spec.o c-family/c-ubsan.o c-family/known-headers.o c-family/c-attribs.o c-family/c-warn.o c-family/c-spellcheck.o arm-c.o glibc-c.o cc1plus-checksum.o libbackend.a main.o libcommon-target.a libcommon.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a libcommon.a ../libcpp/libcpp.a ../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/data/openwrt/staging_dir/host/lib -L/data/openwrt/staging_dir/host/lib -L/data/openwrt/staging_dir/host/lib -lmpc -lmpfr -lgmp -rdynamic -ldl -L./../zlib -lz So, effectively, the creation of cc1plus, which is done in this command, has been failing due to insufficient memory. Curiously, the file cc1plus is still created after that step, but missing the proper permissions: ls -al ./build_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-10.3.0_musl_eabi/gcc-10.3.0-final/gcc/cc1plus -rw-r--r-- 1 adsc adsc 244655320 Sep 15 23:00 ./build_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-10.3.0_musl_eabi/gcc-10.3.0-final/gcc/cc1plus Due to that reason, in subsequent builds Make did see the file and did not rerun the command above. Thus, build then only failed later when the gcc checks were investigating the file and found that it was not set up properly. (And hence, looking at it after the n-th try, I didn't find the root cause in the first place). Calling the command manually (in the correct folder) worked (with the same memory setup), and created a file with proper permissions: ls -al cc1plus -rwxr-xr-x 1 adsc adsc 244655320 Sep 15 23:16 cc1plus Note that the size is exactly the same as for the non-executable file after the failure before. (I did not compare contents). After fixing this (i.e. manually running the command), build continued to run. Internet told me that the "collect2 ..." error means insufficient memory. So, since I never reached the maximum level, I tried to increase the "Startup RAM" and found that this seems to be the solution (4G is already fine for -j12). It appears that although Hyper-V does signal that Dynamic Memory is adjusting values, this is not or not fully working inside the guest. Still, it's quite remarkable that the system reproducibly failed for gcc 10 and 11, while it worked for gcc 8 and 9, and all o
Re: Build issues gcc10
Hi, Adrian, On Mon, 13 Sept 2021 at 23:10, Adrian Schmutzler wrote: > > Just had one try before I went to bed, but it appears the problem is that > cc1plus generated by the toolchain has no execute bit set: How in blazes…? > /data/openwrt/build_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-10.3.0_musl_eabi/gcc-10.3.0-final/./gcc/cc1plus > > If I chmod +x on that file, the build continues. Talk about weirdness…! I'm glad you were able to sort it out, though. Cheers, Rui ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: Build issues gcc10
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Rui Salvaterra > Sent: Sonntag, 12. September 2021 19:12 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org > Subject: Re: Build issues gcc10 > > Hi, Adrian, > > On Sun, 12 Sept 2021 at 15:15, Adrian Schmutzler > wrote: > > > > I'm having build issues with master and (default) gcc10 on ipq targets. > > I don't know about ipq, but I jumped straight to GCC 11.2. Does it make sense > to bother with 10? That said… > > > xgcc: fatal error: cannot execute 'cc1plus': execvp: No such file or > > directory > > … you seem to be missing the C++ compiler. Just had one try before I went to bed, but it appears the problem is that cc1plus generated by the toolchain has no execute bit set: /data/openwrt/build_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-10.3.0_musl_eabi/gcc-10.3.0-final/./gcc/cc1plus If I chmod +x on that file, the build continues. Best Adrian > > Cheers, > Rui > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: Build issues gcc10
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Stefan Lippers-Hollmann > Sent: Montag, 13. September 2021 00:30 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org > Subject: Re: Build issues gcc10 > > Hi > > On 2021-09-12, Adrian Schmutzler wrote: > > Hi, > > > > I'm having build issues with master and (default) gcc10 on ipq targets. > > Just for reference, I've just (successfully) tried an ipq806x build on a long- > standing, but fully updated, Debian/ unstable host, using gcc-10 on the host I was not able to get it working. I tried various additional packages, but no luck. Could you export a list of installed packages on your (working) machine? Best Adrian > > $ gcc --version > gcc (Debian 10.3.0-10) 10.3.0 > Copyright (C) 2020 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is > NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > > and for the OpenWrt build > > $ grep CONFIG_GCC_VERSION .config > CONFIG_GCC_VERSION="10.3.0" > > $ git describe > reboot-17502-g0470159552 > > Rather minimal build-config (no feeds installed), roughly matching the > buildbot configs (just omitting the imagebuilder): > > $ ./scripts/diffconfig.sh > CONFIG_TARGET_ipq806x=y > CONFIG_TARGET_ipq806x_generic=y > CONFIG_TARGET_MULTI_PROFILE=y > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_askey_rt4230w-rev6=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_askey_rt42 > 30w-rev6="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_asrock_g10=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_asrock_g10 > ="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_buffalo_wxr- > 2533dhp=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_buffalo_wx > r-2533dhp="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_compex_wpq864=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_compex_w > pq864="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_edgecore_ecw5410=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_edgecore_ > ecw5410="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_linksys_ea7500-v1=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_linksys_ea7 > 500-v1="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_linksys_ea8500=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_linksys_ea8 > 500="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_nec_wg2600hp=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_nec_wg260 > 0hp="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_nec_wg2600hp3=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_nec_wg260 > 0hp3="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_d7800=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_d7 > 800="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_r7500=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_r7 > 500="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_r7500v2=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_r7 > 500v2="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_r7800=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_r7 > 800="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-ap148- > legacy=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8 > 064-ap148-legacy="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-ap148=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8 > 064-ap148="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-ap161=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8 > 064-ap161="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064- > db149=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8 > 064-db149="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_tplink_ad7200=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_tplink_ad72 > 00="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_tplink_c2600=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_tplink_c260 > 0="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_tplink_vr2600v=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_tplink_vr26 > 00v="" > CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_ubnt_unifi-ac-hd=y > CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_ubnt_unifi- > ac-hd="" >
Re: Build issues gcc10
Hi On 2021-09-12, Adrian Schmutzler wrote: > Hi, > > I'm having build issues with master and (default) gcc10 on ipq targets. Just for reference, I've just (successfully) tried an ipq806x build on a long-standing, but fully updated, Debian/ unstable host, using gcc-10 on the host $ gcc --version gcc (Debian 10.3.0-10) 10.3.0 Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. and for the OpenWrt build $ grep CONFIG_GCC_VERSION .config CONFIG_GCC_VERSION="10.3.0" $ git describe reboot-17502-g0470159552 Rather minimal build-config (no feeds installed), roughly matching the buildbot configs (just omitting the imagebuilder): $ ./scripts/diffconfig.sh CONFIG_TARGET_ipq806x=y CONFIG_TARGET_ipq806x_generic=y CONFIG_TARGET_MULTI_PROFILE=y CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_askey_rt4230w-rev6=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_askey_rt4230w-rev6="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_asrock_g10=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_asrock_g10="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_buffalo_wxr-2533dhp=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_buffalo_wxr-2533dhp="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_compex_wpq864=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_compex_wpq864="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_edgecore_ecw5410=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_edgecore_ecw5410="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_linksys_ea7500-v1=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_linksys_ea7500-v1="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_linksys_ea8500=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_linksys_ea8500="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_nec_wg2600hp=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_nec_wg2600hp="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_nec_wg2600hp3=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_nec_wg2600hp3="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_d7800=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_d7800="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_r7500=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_r7500="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_r7500v2=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_r7500v2="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_netgear_r7800=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_netgear_r7800="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-ap148-legacy=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8064-ap148-legacy="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-ap148=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8064-ap148="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-ap161=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8064-ap161="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_qcom_ipq8064-db149=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_qcom_ipq8064-db149="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_tplink_ad7200=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_tplink_ad7200="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_tplink_c2600=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_tplink_c2600="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_tplink_vr2600v=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_tplink_vr2600v="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_ubnt_unifi-ac-hd=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_ubnt_unifi-ac-hd="" CONFIG_TARGET_DEVICE_ipq806x_generic_DEVICE_zyxel_nbg6817=y CONFIG_TARGET_DEVICE_PACKAGES_ipq806x_generic_DEVICE_zyxel_nbg6817="" CONFIG_ALL_KMODS=y CONFIG_ALL_NONSHARED=y CONFIG_DEVEL=y CONFIG_TARGET_PER_DEVICE_ROOTFS=y CONFIG_TARGET_ALL_PROFILES=y $ ls -gG bin/targets/ipq806x/generic/ insgesamt 442620 -rw-r--r-- 1 3160 13. Sep 00:11 config.buildinfo -rw-r--r-- 1 231 13. Sep 00:11 feeds.buildinfo -rw-r--r-- 1 5892899 13. Sep 00:17 openwrt-ipq806x-generic-askey_rt4230w-rev6-initramfs-uImage -rw-r--r-- 1 6564648 13. Sep 00:17 openwrt-ipq806x-generic-askey_rt4230w-rev6-squashfs-sysupgrade.bin -rw-r--r-- 1 8314584 13. Sep 00:17 openwrt-ipq806x-generic-asrock_g10-initramfs-fit-uImage.itb -rw-r--r-- 1 8388630 13. Sep 00:17 openwrt-ipq806x-generic-asrock_g10-squashfs-nand-factory.bin -rw-r--r-- 1 7803672 13. Sep 00:17 openwrt-ipq806x-generic-asrock_g10-squashfs-nand-sysupgrade.bin -rw-r--r-- 1 5894107 13. Sep 00:17 openwrt-ipq806x-generic-buffalo_wxr-2533dhp-initramfs-uImage -rw-r--r-- 1 6523690 13. Sep 00:17 openwrt-ipq806x-generic-buffalo_wxr-2533dhp-squashfs-sysupgrade.bin -rw-r--r-- 1 8317840 13. Sep 00:17 openwrt-ipq806x-generic-compex_wpq864-initramfs-fit-uImage.itb
RE: Build issues gcc10
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Ansuel Smith > Sent: Sonntag, 12. September 2021 19:50 > To: Adrian Schmutzler > Cc: Rui Salvaterra ; OpenWrt Development List > > Subject: Re: Build issues gcc10 > > > > > > -Original Message- > > > From: Ansuel Smith [mailto:ansuels...@gmail.com] > > > Sent: Sonntag, 12. September 2021 19:18 > > > To: Rui Salvaterra > > > Cc: Adrian Schmutzler ; OpenWrt > > > Development List > > > Subject: Re: Build issues gcc10 > > > > > > Il giorno dom 12 set 2021 alle ore 19:16 Rui Salvaterra > > > ha scritto: > > > > > > > > Hi, Adrian, > > > > > > > > On Sun, 12 Sept 2021 at 15:15, Adrian Schmutzler > > > > wrote: > > > > > > > > > > I'm having build issues with master and (default) gcc10 on ipq > > > > > targets. > > > > > > > > I don't know about ipq, but I jumped straight to GCC 11.2. Does it > > > > make sense to bother with 10? That said… > > > > > > > > > xgcc: fatal error: cannot execute 'cc1plus': execvp: No such > > > > > file or directory > > > > > > > > … you seem to be missing the C++ compiler. > > > > > > A missing dependency for the prereq? Could be that they changed the > > > default package for debian 10 and 11 and nobody notice that? > > > > That was my first suspicion as well, but I didn't really have a good idea > what's missing ... > > > > > > Did you try reinstalling build-essential ? Yes, no change. Also tried various other additional apt packages. Apart from that, the problem seems not to be limited to ipq targets. In general, gcc 8 and 9 seem to build fine, and gcc 10 and 11 fail. Best Adrian > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Build issues gcc10
> > > -Original Message- > > From: Ansuel Smith [mailto:ansuels...@gmail.com] > > Sent: Sonntag, 12. September 2021 19:18 > > To: Rui Salvaterra > > Cc: Adrian Schmutzler ; OpenWrt Development > > List > > Subject: Re: Build issues gcc10 > > > > Il giorno dom 12 set 2021 alle ore 19:16 Rui Salvaterra > > ha scritto: > > > > > > Hi, Adrian, > > > > > > On Sun, 12 Sept 2021 at 15:15, Adrian Schmutzler > > > wrote: > > > > > > > > I'm having build issues with master and (default) gcc10 on ipq targets. > > > > > > I don't know about ipq, but I jumped straight to GCC 11.2. Does it > > > make sense to bother with 10? That said… > > > > > > > xgcc: fatal error: cannot execute 'cc1plus': execvp: No such file or > > > > directory > > > > > > … you seem to be missing the C++ compiler. > > > > A missing dependency for the prereq? Could be that they changed the > > default package for debian 10 and 11 and nobody notice that? > > That was my first suspicion as well, but I didn't really have a good idea > what's missing ... > > Did you try reinstalling build-essential ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: Build issues gcc10
> -Original Message- > From: Ansuel Smith [mailto:ansuels...@gmail.com] > Sent: Sonntag, 12. September 2021 19:18 > To: Rui Salvaterra > Cc: Adrian Schmutzler ; OpenWrt Development > List > Subject: Re: Build issues gcc10 > > Il giorno dom 12 set 2021 alle ore 19:16 Rui Salvaterra > ha scritto: > > > > Hi, Adrian, > > > > On Sun, 12 Sept 2021 at 15:15, Adrian Schmutzler > > wrote: > > > > > > I'm having build issues with master and (default) gcc10 on ipq targets. > > > > I don't know about ipq, but I jumped straight to GCC 11.2. Does it > > make sense to bother with 10? That said… > > > > > xgcc: fatal error: cannot execute 'cc1plus': execvp: No such file or > > > directory > > > > … you seem to be missing the C++ compiler. > > A missing dependency for the prereq? Could be that they changed the > default package for debian 10 and 11 and nobody notice that? That was my first suspicion as well, but I didn't really have a good idea what's missing ... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Build issues gcc10
Il giorno dom 12 set 2021 alle ore 19:16 Rui Salvaterra ha scritto: > > Hi, Adrian, > > On Sun, 12 Sept 2021 at 15:15, Adrian Schmutzler > wrote: > > > > I'm having build issues with master and (default) gcc10 on ipq targets. > > I don't know about ipq, but I jumped straight to GCC 11.2. Does it > make sense to bother with 10? That said… > > > xgcc: fatal error: cannot execute 'cc1plus': execvp: No such file or > > directory > > … you seem to be missing the C++ compiler. A missing dependency for the prereq? Could be that they changed the default package for debian 10 and 11 and nobody notice that? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Build issues gcc10
Hi, Adrian, On Sun, 12 Sept 2021 at 15:15, Adrian Schmutzler wrote: > > I'm having build issues with master and (default) gcc10 on ipq targets. I don't know about ipq, but I jumped straight to GCC 11.2. Does it make sense to bother with 10? That said… > xgcc: fatal error: cannot execute 'cc1plus': execvp: No such file or > directory … you seem to be missing the C++ compiler. Cheers, Rui ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Build issues gcc10
Hi, I'm having build issues with master and (default) gcc10 on ipq targets. Build fails with: true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-O2 -I/data/openwrt/staging_dir/host/include " "CXXFLAGS=-g -O2" "CFLAGS_FOR_BUILD=" "CFLAGS_FOR_TARGET=-Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro" "INSTALL=/data/openwrt/staging_dir/host/bin/install -c" "INSTALL_DATA=/data/openwrt/staging_dir/host/bin/install -c -m 644" "INSTALL_PROGRAM=/data/openwrt/staging_dir/host/bin/install -c" "INSTALL_SCRIPT=/data/openwrt/staging_dir/host/bin/install -c" "LDFLAGS=-static-libstdc++ -static-libgcc " "LIBCFLAGS=-O2 -I/data/openwrt/staging_dir/host/include " "LIBCFLAGS_FOR_TARGET=-Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro" "MAKE=make" "MAKEINFO=/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10. 3.0_musl_eabi/gcc-10.3.0/missing makeinfo --split-size=500 --split-size=500 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/bash" "EXPECT=expect" "RUNTEST=runtest" "RUNTESTFLAGS=" "exec_prefix=/data/openwrt/staging_dir/toolchain-arm_cortex-a7+neon-vfpv4_gc c-10.3.0_musl_eabi" "infodir=/data/openwrt/staging_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10 .3.0_musl_eabi/share/info" "libdir=/data/openwrt/staging_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10. 3.0_musl_eabi/lib" "prefix=/data/openwrt/staging_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10. 3.0_musl_eabi" "tooldir=/data/openwrt/staging_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10 .3.0_musl_eabi/arm-openwrt-linux-muslgnueabi" "AR=ar" "AS=as" "CC=gcc" "CXX=g++" "LD=ld" "LIBCFLAGS=-O2 -I/data/openwrt/staging_dir/host/include " "NM=nm" "PICFLAG=" "RANLIB=ranlib" "DESTDIR=" DO=all multi-do # make make[5]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/zlib' make[5]: Entering directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libbacktrace' make all-am make[6]: Entering directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libbacktrace' true DO=all multi-do # make make[6]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libbacktrace' make[5]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libbacktrace' make[5]: Entering directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libcpp' test -f config.h || (rm -f stamp-h1 && make stamp-h1) make[5]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libcpp' make[5]: Entering directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libdecnumber' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/libdecnumber' make[5]: Entering directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/gcc' /data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_e abi/gcc-10.3.0-final/./gcc/xgcc -B/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl _eabi/gcc-10.3.0-final/./gcc/ -xc++ -nostdinc /dev/null -S -o /dev/null -fself-test=/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-1 0.3.0_musl_eabi/gcc-10.3.0/gcc/testsuite/selftests xgcc: fatal error: cannot execute 'cc1plus': execvp: No such file or directory compilation terminated. make[5]: *** [/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0/gcc/cp/Make-lang.in:178: s-selftest-c++] Error 1 make[5]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final/gcc' make[4]: *** [Makefile:4397: all-gcc] Error 2 make[4]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final' make[3]: *** [Makefile:961: all] Error 2 make[3]: Leaving directory '/data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_ eabi/gcc-10.3.0-final' make[2]: *** [Makefile:91: /data/openwrt/build_dir/toolchain-arm_cortex-a7+neon-vfpv4_gcc-10.3.0_musl_e abi/gcc-10.3.0-final/.built] Error 2 make[2]: Leaving directory '/data/openwrt/toolchain/gcc/final' time: toolchain/gcc/final/compile#1.29#0.21#1.47 ERROR: toolchain/gcc/final failed to build. make[1]: *** [toolchain/Makefile:97: toolchain/gcc/final/compile] Error 1
