[Buildroot] error - machine `ARM-buildroot' not recognized for libpcap

[Buildroot] error - machine `ARM-buildroot' not recognized for libpcap

[John Lemonovich]

[-- Attachment #1.1: Type: text/plain, Size: 2635 bytes --]

I am trying to build a rootfs for an Intel SOC FPGA (Arria 10) using
buildroot.  I've had success in the past but am now trying to build a newer
version FS (Buildroot 2019.11.3 Configuration) and I get stuck at this
error.  Does anyone know how to fix/address the error?  I am adding IPv6
support, and I believe this is required for one or more of the networking
applications I'm including.  I have tried various external toolchains all
with the same result, and this output is from the setting  "Toolchain to be
downloaded and installed".



checking build system type... x86_64-pc-linux-gnu
checking host system type... Invalid configuration
`ARM-buildroot-linux-gnueabihf': machine `ARM-buildroot' not recognized
configure: error: /bin/bash ./config.sub ARM-buildroot-linux-gnueabihf
failed
package/pkg-generic.mk:242: recipe for target
'/us/jlemonovich/skyfather/ipv6/buildroot/output/build/libpcap-1.9.1/.stamp_configured'
failed
make: ***
[/us/jlemonovich/skyfather/ipv6/buildroot/output/build/libpcap-1.9.1/.stamp_configured]
Error 1
make: Leaving directory '/us/jlemonovich/skyfather/ipv6/buildroot'
root@ubuntu18-test:/us/jlemonovich/skyfather/ipv6#
STAGING_DIR="/us/jlemonovich/skyfather/ipv6/buildroot/output/host/ARM-buildroot-linux-gnueabihf/sysroot"
INTLTOOL_PERL=/usr/bin/perl ac_cv_lbl_unaligned_fail=yes
ac_cv_func_mmap_fixed_mapped=yes ac_cv_func_memcmp_working=yes
ac_cv_have_decl_malloc=yes gl_cv_func_malloc_0_nonnull=yes
ac_cv_func_malloc_0_nonnull=yes ac_cv_func_calloc_0_nonnull=yes
ac_cv_func_realloc_0_nonnull=yes lt_cv_sys_lib_search_path_spec=""
ac_cv_c_bigendian=no  ac_cv_header_linux_wireless_h=yes
CFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
 -Os  " CONFIG_SITE=/dev/null ./configure
--target=ARM-buildroot-linux-gnueabihf --host=ARM-buildroot-linux-gnueabihf
--build=x86_64-pc-linux-gnu --prefix=/usr --exec-prefix=/usr
--sysconfdir=/etc --localstatedir=/var --program-prefix=""
--disable-gtk-doc --disable-gtk-doc-html --disable-doc --disable-docs
--disable-documentation --with-xmlto=no --with-fop=no
--disable-dependency-tracking --enable-ipv6 --disable-nls --disable-static
--enable-shared  --disable-yydebug --with-pcap=linux --without-dag
--disable-dbus --disable-bluetooth --without-libnl )
-bash: syntax error near unexpected token `)'
root@ubuntu18-test:/us/jlemonovich/skyfather/ipv6# configure: WARNING:
unrecognized options: --disable-gtk-doc, --disable-gtk-doc-html,
--disable-doc, --disable-docs, --disable-documentation, --with-xmlto,
--with-fop, --disable-dependency-tracking, --disable-nls, --disable-static
configure:: command not found


Thank you,
John

[-- Attachment #1.2: Type: text/html, Size: 2949 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] error - machine `ARM-buildroot' not recognized for libpcap

[Peter Korsgaard]

>>>>> "John" == John Lemonovich <lemonoje@gmail.com> writes:

Hello,

 > I am trying to build a rootfs for an Intel SOC FPGA (Arria 10) using
 > buildroot.  I've had success in the past but am now trying to build a newer
 > version FS (Buildroot 2019.11.3 Configuration) and I get stuck at this
 > error.  Does anyone know how to fix/address the error?  I am adding IPv6
 > support, and I believe this is required for one or more of the networking
 > applications I'm including.  I have tried various external toolchains all
 > with the same result, and this output is from the setting  "Toolchain to be
 > downloaded and installed".

2019.11.3 is EOL, please move to 2022.02.x or 2022.11.x.

With that said, you somehow seem to have changed ARCH to upper case
ARM. Do you have any local modifications?

The host build system type comes from:

package/pkg-autotools.mk:
                --host=$$(GNU_TARGET_NAME) \

Where GNU_TARGET_NAME is defined as:

package/Makefile.in:
# Compute GNU_TARGET_NAME
GNU_TARGET_NAME = $(ARCH)-$(TARGET_VENDOR)-$(TARGET_OS)-$(LIBC)$(ABI)

And where ARCH comes from:

Makefile: ARCH := $(call qstrip,$(BR2_ARCH))

Which for your A9 system gets set in arch/Config.in.arm

config BR2_ARCH
        default "arm"           if BR2_arm
        default "armeb"         if BR2_armeb
        default "aarch64"       if BR2_aarch64
        default "aarch64_be"    if BR2_aarch64_be

So I am not sure how you end up with an upper case 'ARM'?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] error - machine `ARM-buildroot' not recognized for libpcap

[Peter Korsgaard]

>>>>> "John" == John Lemonovich <lemonoje@gmail.com> writes:

Hello,

 > Peter,
 > Thank you for the reply!  I'm not very familiar with the process so I'm
 > relying on the Beginner's Guide and Intel FPGA documentation.  I have built
 > the rootfs successfully for my Arria10 device in the past using buildroot
 > and busybox, but it's been several years since the last time.

 > I am getting the upper case ARM from the Intel FPGA documentation - all
 > through their guides it shows it as upper case:  (see building the root
 > filesystem tab of this link for example)
 > https://www.rocketboards.org/foswiki/Documentation/EmbeddedLinuxBeginnerSGuide

 > Nonetheless, the upper case is apparently incorrect, and I have tried to
 > build with no ARCH specified, which, should default to just 'ARCH=arm',
 > correct?

Yes, you should not define ARCH=<something> (or export it in your
environment) when you use Buildroot. The architecture is specified by
running make menuconfig.


 > I am selecting external toolchain as
 > :gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf
 > My kernel is 5.4.13  from Linux-socfpga

 > I just did a fresh checkout of 2022.02.7  , added a few networking
 > utilities and options, selected external toolchain and prefix and now I get
 > this error:
 > Incorrect selection of kernel headers: expected 5.4.x, got 4.10.x

Your runtime kernel may be 5.4.13, but the Linaro toolchain you mention
above has been built against a 4.10.3 kernel:

cat gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/libc/usr/include/linux/version.h
#define LINUX_VERSION_CODE 264707
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))

printf '0x%x\n' 264707
0x40a03

So you need to configure 'External toolchain kernel headers series' as
4.10.x (or alternatively use one of the newer preconfigured toolchains).

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] error - machine `ARM-buildroot' not recognized for libpcap

[Peter Korsgaard]

>>>>> "John" == John Lemonovich <lemonoje@gmail.com> writes:

Hello,

 >>>> host-gettext-tiny 0.3.2 Downloading
 > wget --passive-ftp -nd -t 3 -O
 > '/us/jl/sfipv6/ipv6/buildroot/output/build/.gettext-tiny-0.3.2.tar.gz.RleKKJ/output'
 > '
 > https://github.com/sabotage-linux/gettext-tiny/archive/v0.3.2/gettext-tiny-0.3.2.tar.gz
 > '
 > --2022-12-19 11:57:14--
 > https://github.com/sabotage-linux/gettext-tiny/archive/v0.3.2/gettext-tiny-0.3.2.tar.gz
 > Resolving github.com (github.com)... failed: Name or service not known.
 > wget: unable to resolve host address ‘github.com’

So you cannot resolve github.com

> wget --passive-ftp -nd -t 3 -O
 > '/us/jl/sfipv6/ipv6/buildroot/output/build/.gettext-tiny-0.3.2.tar.gz.agkwom/output'
 > 'http://sources.buildroot.net/gettext-tiny/gettext-tiny-0.3.2.tar.gz'
 > --2022-12-19 11:57:39--
 > http://sources.buildroot.net/gettext-tiny/gettext-tiny-0.3.2.tar.gz
 > Resolving sources.buildroot.net (sources.buildroot.net)... failed: Name or
 > service not known.
 > wget: unable to resolve host address ‘sources.buildroot.net’

Or sources.buildroot.net

It sounds like you have a DNS issue on your build machine. Please check.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot